-
Notifications
You must be signed in to change notification settings - Fork 7
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
Upgrade to GHC 9.4 #10
Conversation
Thanks, great job @tbidne! I'll take a closer look later next week. @googleson78 could you possibly look at Nix-related issues here please? |
I'll try building on my end as well. |
Same issue reproduces @tbidne are you running NixOS? |
@googleson78 Yes.
I wonder if anyone who has had a successful build recently could share what C libs they are using. |
I had a friend do a successful build of
|
The glibc in the flake/my glibc appears to be the same, which is a pretty bad sign. Not sure what's going on here. |
Same. With the current diff, diff --git a/flake.nix b/flake.nix
index 51906aa..62b067e 100644
--- a/flake.nix
+++ b/flake.nix
@@ -19,9 +19,9 @@
pkgs = import nixpkgs {
inherit system;
};
- in with pkgs-old;
+ in with pkgs;
{
- devShell.x86_64-linux = pkgs-old.mkShell {
+ devShell.x86_64-linux = pkgs.mkShell {
buildInputs = [
pkgs.cabal-install
libffi.dev Which changed |
Ah sorry, I totally forgot to mention that I also did that change before testing. But it seems that didn't really help much. In any case, this seems to be nix(os) exclusive, so maybe we should just merge this with a disclaimer on the flake? |
Fine by me, assuming this works for other users. For the record, I'd like to highlight the message here:
@googleson78 Do you know where this |
Can you build from https://github.com/googleson78/clc-stackage/tree/ghc944? Just so we're 100% on the same page. I'll post my exact error as well a bit later. |
Sure, I get the same error. Also, I figured out the origin of that referenced gcc in the error. Somewhere in the logs there are lines like:
That gcc,
I believe that Thus it appears the error message is coming from |
@tbidne could you please update this line: |
Ah right, one sec. |
I'm happy with the current state of the PR. Would you like to add new packages in a separate PR? |
Sure, I can do that in a separate PR. |
Merged, huge thanks! |
No problem! |
Resolves #6.
Hello, thought I'd take a crack at this. Draft because not everything builds on my machine (see below), but perhaps this is a useful starting point.
Nix build issues
My build issues undoubtedly stem from the nix flake I attempted to use. I see that it is unmaintained -- which is fine -- so I'm opening this PR in case either someone understands the nix problem, or perhaps someone else can verify that it builds without nix, in which case the nix issues are presumably not a blocker.
Click to expand Nix build issues
The error I get is, predictably, related to C dependencies:
This error comes from trying to build
hw-json-simd
. From what I can tell, that__v8hf
symbol comes from libc's intrinsics, so my guess is we need a different libc. I'm not really sure what the right version would be (I get the same error trying to buildmaster
withghc 9.2
), nor is it clear to me how to override the C library that gets linked (naively changing thebuildInputs
doesn't appear to do anything; the same<hash>-gcc-12.2.0
is used). I found these issues (1, 2) but I wasn't able to get anything working.Commenting out the offending libs leads to this classic error:
Also note I updated the flake's
nixpkgs
to explicitly pin the current version and get a more recent version for the newcabal
. Obviously it'd be nicer to have a single pinnednixpkgs
, but I figured it was easier to change as few things as possible to try to get something working first.Bounds
I generated the packages' bounds via a CLI tool. This was a conservative change, merely updating every package's bounds in the current
build-depends
, removing packages that were dropped from stackage nightly. Of course we'd probably want to include new packages as well, but this seemed like an easier starting point.wc
suggests that this PR results in 300 fewer packages.Note I also added a
.gitignore
andindex-state
. I'm happy to remove any of these commits if desired, but I left them in for now as they were useful to me and might be for others.