| 5 Aug 2025 |
Teo (he/him) | You can use https://downloads.haskell.org/ghc/latest/docs/users_guide/debugging.html#ghc-flag-ddump-splices if you want to see the stuff TH outputs | 14:07:00 |
sterni (he/him) | you should also probably try to figure out whether GHC or the linker is the problem | 14:44:05 |
| 6 Aug 2025 |
| Mikel Pérez changed their profile picture. | 02:53:36 |
| 7 Aug 2025 |
| J. Ryan Stinnett joined the room. | 13:34:41 |
| 8 Aug 2025 |
| 0x4A6F joined the room. | 06:54:24 |
sterni (he/him) | teo (they/he): is there an issue alreday for the issue that finalStage = Stage2 is silently ignored? | 10:06:06 |
Teo (he/him) | Not as far as I know. it would be good to make one | 10:07:18 |
Teo (he/him) | even if there is one, it would put it back on folks' radar | 10:07:32 |
sterni (he/him) | https://gitlab.haskell.org/ghc/ghc/-/issues/26289 | 10:45:58 |
sterni (he/him) | let's try this again https://discourse.nixos.org/t/call-for-contributions-we-are-updating-to-ghc-9-10-2/67756 (lmk about any typos) | 11:36:01 |
sterni (he/him) | funny that we did 9.2, 9.4, 9.6 and 9.8 without ever posting on discourse | 11:36:26 |
sterni (he/him) | though 8.10 -> 9.0 truly was the big one | 11:36:36 |
sterni (he/him) | I'm a bit concerned people will be scared away by this wall of text, but I'm the wrong person to write a short post. Also documentation on contributing to haskellPackages is really spotty. | 11:38:41 |
sterni (he/him) | The short intro I wrote (and copied here) for 9.0.2 post is kinda good, maybe we should just put that in the Nixpkgs manual as a starting point. | 11:39:11 |
chreekat | It's an excellent post | 11:59:28 |
| @selkie-diligent-61ad45186da03739848be880:gitter.im left the room. | 13:55:04 |
emily | has anyone noticed a GHC build hanging around building ghc-9.8.4 (buildPhase): | Run Ghc CompileCWithGhc Stage1: rts/Hash.c => _build/stage1/rts/build/c/Hash.thr_debug_dyn_o with a bunch of C compilers using all the CPU they can find overnight but seemingly not progressing | 14:11:44 |
emily | (I suspect the answer is no and this is an LLVM 21 regression but I thought I'd check) | 14:11:53 |
maralorn | sterni: Excellent post. I found two typos in the paragraph
When you’ve found a fix for a package, make sure to add a comment next to your override explaining explaining why it is needed and ideally link an issue or PR that needs to be resolved upstream for us to drop the override (if no issue exist, do open one).
Their is a double "explaining" and "no issue exist" is missing numerus congruency.
| 16:38:06 |
maralorn | * sterni: Excellent post. I found two typos in the paragraph
When you’ve found a fix for a package, make sure to add a comment next to your override explaining explaining why it is needed and ideally link an issue or PR that needs to be resolved upstream for us to drop the override (if no issue exist, do open one).
There is a double "explaining" and "no issue exist" is missing numerus congruency.
| 16:38:39 |
sterni (he/him) | emily: nope and I have compiled a quite a few GHCs on haskell-updates the last week | 17:07:09 |
sterni (he/him) | though x86_64-linux so no LLVM involvement at all | 17:07:37 |
| 9 Aug 2025 |
| crtschin joined the room. | 01:58:10 |
| danl joined the room. | 05:01:30 |
emily | how does one understand why a non-Stackage package is several major versions old in the Haskell package set? would it be because of things requiring an older version, or are Hackage packages not bumped en masse at all? | 22:03:17 |
emily | llvm-tf is at 16.0 and I don't immediately see why – seems like the stuff pinning llvm-* to old versions are already marked broken | 22:04:57 |
sterni (he/him) | because the llvm-tf > 16 versions have only been uploaded a month ago | 22:08:41 |
sterni (he/him) | staging is on 21.0 | 22:08:47 |
emily | ah I didn't notice that even 17.0 was so recent… thank you | 22:10:26 |
sterni (he/him) | you should be able to find out by grepping pkgs/development/haskell-modules/configuration-* if it should be the case | 22:11:30 |