-
-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
libffi stopped working recently on nixos-rebuild #52283
Comments
looks like |
For future debugging, you should always include config.log when the configure script fails. Reproducing it, this is the error:
The breaking commit appears to be: beb063a not sure what is going on though. |
@matthewbauer FWIW, I came to the same conclusion via git bisect (starting based on hydra builds https://hydra.nixos.org/build/85622858)
Isn't nixos-unstable supposed to receive updates from master only after the build succeeds on hydra? |
I don't think it's actually libffi that broke... It's just the way gnustep-base is tesing libffi, namely
In particular, note Rather strangely, earlier tests specifically for bfd seem to have succeeded. Eg:
I'm not sure how... |
Before beb063a, binutils included a libbfd install, which is now being removed in postFixup beb063a#diff-c59ce5deea2f4002004fffdb11c5ed57R131 Fixes #52283
Nice work! I suspect that libbfd is hardcoded into clang somewhere. For whatever reason it does not pick up the right location though.
This is true for certain things that are blocking jobs (or dependencies of those jobs). They are listed here: https://hydra.nixos.org/job/nixos/trunk-combined/tested#tabs-constituents but right now we don't have gnustep or unar in any of these. |
Oh ok, I suppose blocking only on "important" things makes sense. Also, thinking about it a little more, I'm not entirely sure libbfd needs to be in |
hi, i'm still getting this error, what can i do to debug/fix this? |
fwiw, I have this error when building |
Issue description
i ran
sudo nixos-rebuild switch --upgrade
today and got this error:Steps to reproduce
Technical details
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste theresults.
The text was updated successfully, but these errors were encountered: