Building all Stackage executables #4
Assignees
Comments
|
Output of the first try at this commit: static-haskell-nix/survey/default.nix Lines 257 to 259 in 09d0eaa It took around 3 hours to get there (I built with 5 machines). The final status line, The program didn't terminate; right now it's
Insights:
|
60 tasks
|
I have now killed Cleaned up, these packages failed the first try to build:
|
Edit: Newer numbers
Original numbersI have further reduced the number of build errors as of commit 7e41d26. I also added functionality to inform nix Haskell packages to Statistics
By specifying some more dependencies, this can probably be reduced further significantly. But I think this is good enough for now. So I'm closing this ticket as done. Non-building packagesThe 30 packages that currently don't build are: Full build errors |
|
With my update to NixOS/nixpkgs@88ae8f7 as per #6, now 7 more packages fail but we also have 4 more executables, so with that we're at Total set of 37 failing exes: |
nh2
added a commit
that referenced
this issue
Oct 24, 2018
Works on stack commit f9d0042c141. The changes are necessary because stack-1.9.1 explicitly depends on Cabal-2.4.0.1 in its stack.yaml which is pulled in via stack2nix. Doing this, I also found that the way I patched Cabal so far was not really optimal, because not only for stack, but in general my patches for Cabal wouldn't be used if the Cabal version wasn't the default one in nixpkgs. Now instead I use patches instead of a Github fork so that they can be applied to any Cabal version. Also added is a framework for backwards compatibility in the situation that upstream Cabal starts merging my patches and they appear in nixpkgs. I've also checked that there's no regression to the set of all Stackage executables that can be built (#4) and added the non-working ones explicitly into the survey file.
nh2
added a commit
that referenced
this issue
Dec 19, 2018
Works on stack commit f9d0042c141. The changes are necessary because stack-1.9.1 explicitly depends on Cabal-2.4.0.1 in its stack.yaml which is pulled in via stack2nix. Doing this, I also found that the way I patched Cabal so far was not really optimal, because not only for stack, but in general my patches for Cabal wouldn't be used if the Cabal version wasn't the default one in nixpkgs. Now instead I use patches instead of a Github fork so that they can be applied to any Cabal version. Also added is a framework for backwards compatibility in the situation that upstream Cabal starts merging my patches and they appear in nixpkgs. I've also checked that there's no regression to the set of all Stackage executables that can be built (#4) and added the non-working ones explicitly into the survey file.
This |
|
With my new branch |
|
The error from above #4 (comment) is: |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I plan to build as many executables from Stackage as possible, statically.
This is to
The text was updated successfully, but these errors were encountered: