-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Cannot pass flags to bootstrap links after #133092 #136984
Comments
cc @madsmtm |
We currently cannot build Rust for Chromium's toolchain due to this regression. If it takes a while to resolve this, can we revert #133092 in the meantime to keep HEAD functional? |
Sorry, should've commented here earlier. I'm working on a fix in |
Another workaround in the meantime would be for you to pass |
the |
…for upstream issue And remove upstream rust revert. Suggested at rust-lang/rust#136984 (comment). Tested locally that removing the revert causes the build to break and the CFLAGS workaround fixes it again, so there shouldn't be a need for a new package. Bug: 395891130 Change-Id: Iae7fc9e518e6ff955a09385f5443fac54ca6a015 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6269907 Commit-Queue: Arthur Eubanks <aeubanks@google.com> Reviewed-by: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/main@{#1420683}
Summary
(https://crbug.com/395891130 is the bug on our side)
After #133092, flags we set via
CFLAGS
/CXXFLAGS
/LDFLAGS
/RUSTFLAGS_BOOTSTRAP
/RUSTFLAGS_NOT_BOOTSTRAP
no longer get passed to bootstrap links, resulting in the--sysroot=
flag we pass not taking effect (they get passed to the compiles but not to the link) and getting weird link errors. I've commented on that PR with the location of which change breaks us. Looking at the PR, it seems like it's not possible to pass arbitrary link flags anymore, which seems like a big regression.Command used
Expected behaviour
Build succeeds
Actual behaviour
Operating system
Debian
HEAD
6171d94
Additional context
with
RUST_BACKTRACE=1
and-v
The text was updated successfully, but these errors were encountered: