-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Linking with cargo-zigbuild
failed on armv7-unknown-linux-{gnu, musl}eabihf
due to missing symbols
#108392
Comments
#108307 should have fixed the |
I see that the warnings for the unsupported I also see that every linking errors have Looking at the PR merged on the 2023-02-19 I don't see anything suspect. Could you try using cargo-rustc-bisect with a custom script to try to find the the commit that regressed your workflow. |
I've tried disabling cross-lang-lto and feature "zstd/cross-lang-fat-lto". It could be a lto problem, since the debug build, which does not turn on lto, works just fine.
Yeah I could try this tomorrow. |
I'm using:
And then I am running Edit: It didn't work, will figure it out tomorrow. |
@Urgau Running:
gives me:
which is strange, because this is the one that worked. |
The bisection wasn't successful. I would recommend using But I wouldn't be surprised if |
@Urgau I got a panic when using
|
Have you removed the |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@Urgau Seems that 2023-02-15 contains the regression:
|
Command I ran:
|
I just upgrade to
|
I setup-ed an archlinux container to try to bisect it myself and I was unable to find any working toolchain with your args (I search from 2023-02-10). This makes me wonder if it is a regression at all, maybe it just work by accident. Who knows. Second I think you are missing Third I was able to build
ie, without To be clear, the only thing that made a difference was removing the Fourth, if this is indeed a regression it's not one from stable (since I'm able to build it from stable with @rustbot label: +regression-from-nightly-to-nightly -regression-from-stable-to-nightly Lastly, I've reached my (current) limits on my debugging abilities. Maybe if we had a regression I could have help more but without one I don't know what to do now. Sorry. |
@Urgau Thank you, removing
|
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-medium |
For reference, here are the salient parts of these logs (GitHub Actions keeps these for 90 days before they are automatically deleted): Details
Details
This looks similar to issue #108853. |
release-builds / armv7-unknown-linux-musleabihf
release-builds / armv7-unknown-linux-gnueabihf
This can be reproduced by running:
Or by running the following cmds on the clone:
The CI failed with several missing symbols.
Also,
cargo-zigbuild
failed to handle several link args:Version it worked on
It most recently worked on:
rust version 1.69.0-nightly (7aa413d59 2023-02-19)
Version with regression
@rustbot modify labels: +regression-from-stable-to-nightly -regression-untriaged
The text was updated successfully, but these errors were encountered: