dylib crate fails to compile

[Dotnet-x86]

I tried this code and run: demo.zip

Code

cargo run dev

Engine

lib.rs

pub fn run () {
    println!("Hello from engine");
}

cargo.toml

[package]
name = "engine"
version = "0.1.0"
edition = "2024"

[dependencies]

[lib]
crate-type = ["dylib"]

Editor

main.rs

extern crate engine;
fn main() {
    engine::run();
    println!("Hello from editor");
}

cargo.toml

[package]
name = "editor"
version = "0.1.0"
edition = "2024"

[dependencies]
engine = {path = "../engine"}

workspace.cargo.toml

[workspace]
resolver = "2"
members = [ "editor","engine"]

I expected the dylib crate to work correctly as a dependency, allowing the binary to dynamically link to it and run without issues.

Instead, this happened:

Details

PS C:\Users\{}\Documents\Rust\development> cargo run dev
   Compiling editor v0.1.0 (C:\Users\compl\Documents\Rust\development\editor)
error: cannot satisfy dependencies so `engine` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away
  = note: `engine` was unavailable as a static crate, preventing fully static linking     

error: cannot satisfy dependencies so `core` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `alloc` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `compiler_builtins` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `rustc_std_workspace_core` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `unwind` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `cfg_if` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `hashbrown` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `rustc_std_workspace_alloc` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `std_detect` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `rustc_demangle` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `windows_targets` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: cannot satisfy dependencies so `panic_unwind` only shows up once
  |
  = help: having upstream crates all available in one format will likely make this go away

error: could not compile `editor` (bin "editor") due to 13 previous errors

Tools

rustc --version --verbose:

rustc 1.87.0-nightly (9fb94b32d 2025-03-10)
binary: rustc
commit-hash: 9fb94b32df38073bf63d009df77ed10cb1c989d0
commit-date: 2025-03-10
host: x86_64-pc-windows-msvc
release: 1.87.0-nightly
LLVM version: 20.1.0

[Noratrieb]

Thank you for the report! It would be useful to bisect the regression using cargo-bisect-rustc to make it easier to figure out what happened and ping the relevant people.
@rustbot label E-needs-bisection

[moxian]

cargo-bisect-rustc output attached, but I appear to be too tired to intelligently triage it myself right now:

take2:

searched toolchains nightly-2020-04-23 through nightly-2024-06-07


********************************************************************************
Regression in nightly-2021-03-15
********************************************************************************

fetching https://static.rust-lang.org/dist/2021-03-14/channel-rust-nightly-git-commit-hash.txt
nightly manifest 2021-03-14: 40 B / 40 B [=======================================================] 100.00 % 76.44 KB/s converted 2021-03-14 to acca818928654807ed3bc1ce0e97df118f8716c8
fetching https://static.rust-lang.org/dist/2021-03-15/channel-rust-nightly-git-commit-hash.txt
nightly manifest 2021-03-15: 40 B / 40 B [======================================================] 100.00 % 250.40 KB/s converted 2021-03-15 to d6eaea1c8860adb5302d2fbaad409e36585ab217
looking for regression commit between 2021-03-14 and 2021-03-15
fetching (via remote github) commits from max(acca818928654807ed3bc1ce0e97df118f8716c8, 2021-03-12) to d6eaea1c8860adb5302d2fbaad409e36585ab217
ending github query because we found starting sha: acca818928654807ed3bc1ce0e97df118f8716c8
get_commits_between returning commits, len: 8
  commit[0] 2021-03-13: Auto merge of #83064 - cjgillot:fhash, r=jackh726
  commit[1] 2021-03-14: Auto merge of #83105 - JohnTitor:rollup-tqpm8pb, r=JohnTitor
  commit[2] 2021-03-14: Auto merge of #83028 - GuillaumeGomez:prevent-js-error-if-no-filter, r=Nemo157
  commit[3] 2021-03-14: Auto merge of #83094 - GuillaumeGomez:crates-js-location, r=Nemo157
  commit[4] 2021-03-14: Auto merge of #83044 - kubo39:set-llvm-code-model, r=nikic
  commit[5] 2021-03-14: Auto merge of #83082 - cjgillot:defkey-ii, r=oli-obk
  commit[6] 2021-03-14: Auto merge of #82399 - petrochenkov:modin2, r=Aaron1011
  commit[7] 2021-03-14: Auto merge of #83062 - JohnTitor:improve-reassign-err, r=davidtwco
ERROR: no CI builds available between acca818928654807ed3bc1ce0e97df118f8716c8 and d6eaea1c8860adb5302d2fbaad409e36585ab217 within last 167 days

old incorrect bisection attempt. don't look

searched toolchains nightly-2019-11-05 through nightly-2024-06-07

********************************************************************************
Regression in nightly-2020-04-23
********************************************************************************

fetching https://static.rust-lang.org/dist/2020-04-22/channel-rust-nightly-git-commit-hash.txt
nightly manifest 2020-04-22: 40 B / 40 B [=======================================================] 100.00 % 48.67 KB/s converted 2020-04-22 to 45d050cde277b22a755847338f2acc2c7b834141
fetching https://static.rust-lang.org/dist/2020-04-23/channel-rust-nightly-git-commit-hash.txt
nightly manifest 2020-04-23: 40 B / 40 B [=======================================================] 100.00 % 82.64 KB/s converted 2020-04-23 to b2e36e6c2d229126b59e892c9147fbb68115d292
looking for regression commit between 2020-04-22 and 2020-04-23
fetching (via remote github) commits from max(45d050cde277b22a755847338f2acc2c7b834141, 2020-04-20) to b2e36e6c2d229126b59e892c9147fbb68115d292
ending github query because we found starting sha: 45d050cde277b22a755847338f2acc2c7b834141
get_commits_between returning commits, len: 7
  commit[0] 2020-04-21: Auto merge of #71170 - spastorino:dyn-fnonce-alignment, r=nikomatsakis
  commit[1] 2020-04-22: Auto merge of #71402 - ehuss:update-cargo, r=ehuss
  commit[2] 2020-04-22: Auto merge of #71410 - JohnTitor:rollup-vh6dut5, r=JohnTitor
  commit[3] 2020-04-22: Auto merge of #71323 - nnethercote:bitcode-in-rlib, r=alexcrichton
  commit[4] 2020-04-22: Auto merge of #71424 - Dylan-DPC:rollup-iunh61a, r=Dylan-DPC
  commit[5] 2020-04-22: Auto merge of #71374 - nnethercote:alphabetize-C-and-Z-options, r=petrochenkov
  commit[6] 2020-04-22: Auto merge of #71431 - Dylan-DPC:rollup-rvm6tfy, r=Dylan-DPC
ERROR: no CI builds available between 45d050cde277b22a755847338f2acc2c7b834141 and b2e36e6c2d229126b59e892c9147fbb68115d292 within last 167 days

[bjorn3]

My best guess would be that #71402 for some reason changed cargo to no longer pass -Cprefer-dynamic in this case.

Also cc https://users.rust-lang.org/t/cargo-build-error-cannot-satisfy-dependencies-so-only-shows-up-once-dylib/126800

[moxian]

Sorry, the bisection above is completely wrong, because I didn't double check that it regresses in the desired way on the version cargo-bisect-rustc provides. This work now needs to be redone by someone who is more awake than me.
My apologies.

Edit: re-ran the bisection, double-checked the results, updated my comment above. Apologies for the spam and confusion once again.

[Dotnet-x86]

Still running cargo bisect-rustc but haven't found a working version yet.

[tgross35]

Do you know this worked in a previous version? If not then you probably don't have to hunt for a working version, it may never have built correctly. If so, then you should be able to pass that version to cargo-bisect-rustc with --start.