-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nightly CI failed: collect2: fatal error: cannot find 'ld' #31
Comments
nightly-2024-05-18 is the first bad nightly, nightly-2024-05-17 still works. @lqd any idea why that would break the build here...? I'm not doing anything weird wrt linking that I am aware of. I am building custom sysroot (which still works fine) and then building a crate against that, and then somehow that can't find the linker?!? |
My main confusion is why it is even trying to run The other odd thing is the paths cargo/rustc have set:
and also It seems almost as if it is taking the sysroot path and then walking the file system from there, but that's entirely wrong when the sysroot is overwritten with a locally built one. |
Yeah, rust-lld is supposed to be in the tools search paths, and rustc adds them to the linker invocation. You can revert back to the default linker with rust-lld has been present in the sysroot for a long time and is used by default by some other targets, so I wonder if the sysroot here is just incomplete. |
That's possible -- I assumed a sysroot is complete by just filling it with the output of the standard library build. That worked so far 🤷 |
I don't know how cargo-careful works or how your sysroot is built but:
|
I will likely do the sysroot copying. Bootstrao can't help as there is no rustc checkout involved here.
Is there some way to know all the files/folders that need copying? I guess for now I will just copy "bin".
|
For a general sysroot I couldn't say -- especially with sanitizers, self-contained linking and their object files, etc -- but for this case copying |
I have no idea what's going on: the test crate doesn't build any more in the cronjob, with a linker error that makes no sense.
The text was updated successfully, but these errors were encountered: