-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Upgrading to nixpkgs master #6
Comments
Trying nh2/nixpkgs@efb033a, I get an issue compiling
My system gcc understands it:
CC @dtzWill |
|
Pretty sure the reason is the upgrade to musl 1.1.20 (NixOS/nixpkgs#46064); the commit NixOS/nixpkgs@e37c21c itself fails with that message but the commit before it, NixOS/nixpkgs@88ae8f7, doesn't. |
Oh, I don't see this locally because I'm using the fix I committed to staging that addresses this :P. Sorry about that. Can you try using that patch (however works best for you) and LMK if that fixes the issue for you (especially if it doesn't!). This PR: NixOS/nixpkgs#45703 |
@dtzWill I see. Why did it work before though? Why does the musl update make this difference? |
On NixOS/nixpkgs@88ae8f7 I also get a Cython build failure due to failing tests (when building sphinx, a dependency of servant):
Note this takes quite long to run: |
Don't suppose bumping to latest cython fixes things? O:) Given the comments in the nix expression you linked disabling tests doesn't seem so bad BUT it'd be good to check the reasons for the failures first... :/. |
I can reproduce it in the build environment; it looks a bit cleaner there:
I get 2 failures here though, and now the signal number is different. |
The The other one can be reproduced quickly like this (the last CLI argument is a match on a test name):
That's much quicker than waiting 40 minutes for all the tests. |
Workaround for the Cython issue: Disabling tests with And this other workaround for another issue also works: pyca/pyopenssl#768 (comment) |
Getting some
(CC @Ericson2314 @dtzWill)
|
Note that we can't upgrade to the latest master yet because musl 1.1.20 breaks things vs 1.1.19 (see #6).
I'm also having a trouble the tests for As opposed to the above Cython test issues with Python 2.7, it doesn't show test failures, only hangs forever. |
I've now worked around all of these issues affecting the upgrade to musl-1.1.19 on my branch I can build the I haven't put in time for support for newer nixpkgs with musl-1.1.20 based on nixpkgs staging yet. |
@nh2 you can just remove that assert. I think i was generalizing whatever was there before. A More generally, any chance of being able to get this onto 18.09 too? I might have a few cycles to help now, finally. |
I'm not sure openjdk was working with musl previously--something must be requiring it now that didn't previously (not at all related to 1.1.19 vs 1.1.20). If you have any additional problems you're seeing that appear related to musl (or if you're not sure, of course!) please liberally cc me so I can take a look. Hope to get things working for you soon! |
@Ericson2314 Which part would you like to get into 18.09? An overlay ala https://github.com/nh2/static-haskell-nix/blob/7ad63b1ab4168e4a97396dddfe59a11a5e3c6f43/survey/default.nix so that Hyda would build at least some static executables from the If yes, sounds like a good idea to ensure that things keep working as stuff like musl is upgraded. Where in nixpkgs should that be placed? |
@nh2 Well even better than that overlay incorperate things into the packages proper; I guess I just disagree with those saying it isn't worth it to make a "static nixpkgs": there's tons of |
@Ericson2314 I agree with you, and am happy to help with that effort. I think it would be awesome if I could request static exes from all kinds of executables easily via nix, and have cache.nixos.org deliver them trivially. |
|
Note for myself: Probably also want NixOS/nixpkgs#47278 via NixOS/nixpkgs#46923 (comment). |
Over the last days I've been working on an update to the current nixpkgs master, on branches starting with Problems I encountered (to be updated as I go along) and dealt with:
Extra abilities unlocked:
|
I did another big master-pin update in #61. |
Another big update to |
The latest nixpkgs
master
has all fixes I had in my nixpkgs commit 50677e464359947f2a71cfd497c4022e3cdf8c7d.So I'd like to just switch to a nixpkgs master commit.
The text was updated successfully, but these errors were encountered: