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
rust: fix glibc build #34205
rust: fix glibc build #34205
Conversation
There currently are two more approaches to fix
|
@@ -101,6 +101,10 @@ stdenv.mkDerivation { | |||
# Useful debugging parameter | |||
# export VERBOSE=1 | |||
'' | |||
+ optionalString (stdenv ? glibc) '' | |||
# Disable test for glibc-2.26 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: it's patched glibc-2.25.
I think disabling the whole test as in this PR is the best way, at least for now. |
Yeah, unless it really is a glibc bug ofcorse but doesn't look like that's the case. |
One thing that irritates me is that the test remains unchanged in newest |
... after applying glibc patches. It's not clear (yet) why this older rustc (test) got broken. Newer rustc (used for Firefox) has the very same test that still passes.
Strange, but I see no use in delaying any more. We can improve later, when/if we find out more. |
Oh of course! I'm happy there is a solution to the issue in. Thanks for merging. |
Motivation for this change
Tested rustc, cargo and a few rust packages.
/cc @vcunat
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)