| 6 Sep 2025 |
 emily | well, it works enough on 9.4 with my patches to build GHC itself at least… | 18:29:30 |
| emily | but yeah I don't get the impression there is much care for it | 18:29:53 |
| emily | even the LoongArch64 person making an mcmodel fix was like "this isn't a good fix because we should just have NCG" | 18:30:03 |
 sterni (he/him) | true, but we don't really exercise it with later versions of GHC I think | 18:30:04 |
| emily | I did my best, though, in terms of backporting everything LLVM-version-relevant | 18:30:30 |
| emily | pretty sure I was more thorough than upstream is when bumping from what i saw | 18:30:52 |
| sterni (he/him) | yes, I did not find anything you missed; except for a fix for llvm-ar >= 17, but that's unrelated to the llvmPackages we take as an input | 18:35:04 |
| sterni (he/him) | I think worrying about hostPlatform.useLLVM is for some other time | 18:35:24 |
| emily | hm would that not be picked up from the wrapping we do? | 18:37:59 |
| emily | ah I guess it would still just use the regular ar by default? | 18:38:00 |
| emily | not sure what ar we use on Darwin tbh | 18:38:00 |
| sterni (he/him) | I think GHC just uses AR, but that's only llvm-ar if useLLVM in nixpkgs (or does darwin use it?). As such it's also controlled by the global default LLVM version, so orthogonal to what we're doing | 19:21:28 |
| emily | right | 19:30:57 |
| emily | I think we might be switching to using more LLVM bintools on Darwin ~soon | 19:31:05 |
| emily | so it would become relevant then I suppose | 19:31:08 |
| 7 Sep 2025 |
| emily | a hidden message from the gods, the lost last great GHC version:
pkgs/development/haskell-modules/hackage-packages.nix
115923: sha256 = "06y0pz0rny9pbm5lzc6n64zdf7139dgwbghc908vzndm6pcjrs5h";
| 00:23:53 |
| sterni (he/him) | trust me bro 6 more minor releases and GHC 9.0 is going to be good just 6 more | 00:37:44 |
| sterni (he/him) | 
Download 20250907_02h36m10s_niri.png | 00:37:59 |
| sterni (he/him) | do you think this thunderbird bug is trying to tell me something | 00:38:07 |
| emily | I looked at that screenshot before seeing the message and was like yeah that's slightly more than I expected but I guess there have been a lot of PR comments today | 00:42:16 |
| sterni (he/him) | I do not remember how I fixed this last time and it does not seem to be affected by restarting, so I'm stuck with you indefinitely | 10:50:38 |
 Wolfgang Walther | Looks like corruption in the thunderbird profile. What helped me in this case was deleting the respective file in ~/.thunderbird/.../ImapMail/... and downloading it again. Of course.. only do that with IMAP, not with POP3. | 11:00:10 |
| sterni (he/him) | Yeah, I think I deleted and redownloaded something last time. | 11:02:01 |
 maralorn | Huh, a wild wolfgangwalther appeared. | 11:12:14 |
 bglgwyng | I'm trying to let Nix fetch index-tarball and cabal use it.
repository hackage.haskell.org
url: file://${./01-index.tar.gz}
But it didn't work. Has anyone tried something similar?
| 12:56:25 |
| bglgwyng | I read https://cabal.readthedocs.io/en/3.4/installing-packages.html this page, and I don't even sure that it's possible to configure a repository only with the index tarball only. | 12:56:50 |
| bglgwyng | I just tried url: file://${repo} which contains 00-index.tar.gz and got
> cabal-install version 3.14.2.0
> compiled using version 3.14.2.0 of the Cabal library
> Warning: Caught exception during _mirrors lookup:res_query: does not exist
> (Connection refused)
> Warning: No mirrors found for
> file:///nix/store/7kry9ps6yridc97gpp4kp8vcd99vlnyx-repo
> /nix/store/7kry9ps6yridc97gpp4kp8vcd99vlnyx-repo/root.json: openBinaryFile: does not exist (No such file or directory)
| 13:42:39 |
| bglgwyng | For some reasone, cabal behaves differently from my local cabal(not in Nix sandbox). | 13:43:12 |
 toonn | Builds are sandboxed by default on Linux, so network access outside of FODs is prohibited. | 13:54:05 |
 chreekat | yes, but that's an unrelated warning. @bglgwyng:matrix.org the error is that cabal is looking for a file 'root.json' next to the tarball. Still I think you'll run into other problems eventually... That root.json is part of a partial TUFT implementation that is gonna look at timestamps and isn't reproducible | 14:00:30 |
