| 12 May 2025 |
 vaibhavsagar | cool, I do have a (large) repro so I'll try that | 23:54:36 |
| 13 May 2025 |
| vaibhavsagar | thanks, I opened https://gitlab.haskell.org/ghc/ghc/-/issues/26033 | 00:04:56 |
 chreekat | does cabal --enable-executable-static work on NixOS? I just get a ton of endefined references to everything from the linker | 13:32:14 |
| chreekat | * does cabal --enable-executable-static work on NixOS? I just get a ton of undefined references to everything from the linker | 13:32:20 |
 winston | this might help, depending on your dependencies it can be quite involved | 17:11:42 |
 maralorn | Does anyone know whether overriding ghc works via ghc = … super.ghcin a haskellPackages overlay? | 17:44:24 |
| chreekat | winston: i think doing it in a nix build is actually somewhat more explored than what I am trying to do, which is just use cabal in a nix shell | 18:40:05 |
 Alex | In reply to @maralorn:maralorn.de
Does anyone know whether overriding ghc works via ghc = … super.ghcin a haskellPackages overlay? My understanding of how the whole thing is wired suggests that it ought to work. | 19:40:06 |
| 14 May 2025 |
 sterni (he/him) | probably is broken in some way | 14:26:11 |
| sterni (he/him) | Anything blocking https://github.com/NixOS/nixpkgs/pull/404362? I think it can be merged. | 14:27:05 |
 thirdofmay18081814goya | it's not normal for template-haskell not to appear in the global package db for ghc66 right? | 15:12:06 |
| thirdofmay18081814goya | by global package db I mean the path given by ghc --info | 15:12:17 |
| thirdofmay18081814goya | or equivalently (i just learned) ghc-pkg list | 15:19:05 |
| thirdofmay18081814goya | seems to be an issue with haskell.nix's shell function | 15:53:31 |
| sterni (he/him) | unfortunately, this is the wrong place to ask about haskell.nix. You would expect template-haskell-2.20.0.0. | 16:08:21 |
| thirdofmay18081814goya | right, turns out it is a haskell.nix specific problem, no issue with the standard infra | 16:18:50 |
| thirdofmay18081814goya | (ty for answer) | 17:20:27 |
| thirdofmay18081814goya | * (ty for answer, forgot lol) | 17:20:46 |
| thirdofmay18081814goya | * (ty for answer) | 17:21:26 |
|  keypusher joined the room. | 17:44:11 |
| keypusher | What is a good approach building a multi library project with nix? It seems cabal 3's "multiple libraries per cabal file" doesn't play well with nix. Which leads me to believe it's a better bet to keep separate cabal file per library? | 18:25:02 |
| keypusher | "seems" here is from memory and also google search on the subject that led me to a thread that seems to confirm it didn't work well by end of 2024. | 18:28:44 |
 alexfmpe | "doesn't play well with nix" ? | 19:18:45 |
| 15 May 2025 |
 Profpatsch | keypusher: yeah I’d assume with the nixpkgs haskell system you need a separate cabal | 17:17:13 |
| Profpatsch | dunno about haskell.nix | 17:17:22 |
| alexfmpe | I'm confused on what the issue is | 18:00:54 |
| alexfmpe | There's plenty of multi component packages on nixpkgs | 18:01:13 |
| alexfmpe | well, I guess one ergonomic issue I'm aware of is a single callCabal2nix derivation will build all components with different flags or for different platforms | 18:05:10 |
| alexfmpe | * well, I guess one ergonomic issue I'm aware of is a single callCabal2nix derivation will build all components with the same flags for the same platform, etc | 18:05:25 |
| alexfmpe | so if you wanted different flags for each you'd need to build all the components with each configuration | 18:05:55 |
