| 5 Jan 2026 |
 bake.monorail | Alyssa Ross: any chance you can take another look to #458935? John Ericson made some other suggestions that have been implemented. | 10:50:27 |
| 6 Jan 2026 |
| bake.monorail | Thanks <3 I'm so happy :) | 17:49:19 |
| 9 Jan 2026 |
 alexfmpe | where do platform symbols like loongarch come from?
I hit symbol issues in libffi when trying to build cross-compiling GHC on several platforms
For instance, I'm getting https://github.com/libffi/libffi/blob/2263d6037f8ef6b8d5bef14117ad1a17c32a20b9/src/loongarch64/ffitarget.h#L66
which should mean __loongarch64 isn't defined, but loongarch is or the error on line 39 would trigger first
I see both of them in https://loongson.github.io/LoongArch-Documentation/LoongArch-toolchain-conventions-EN.html but don't know where they're supposed to come from | 12:07:45 |
| alexfmpe | * where do platform symbols like __loongarch__ come from?
I hit symbol issues in libffi when trying to build cross-compiling GHC on several platforms
For instance, I'm getting https://github.com/libffi/libffi/blob/2263d6037f8ef6b8d5bef14117ad1a17c32a20b9/src/loongarch64/ffitarget.h#L66
which should mean __loongarch64 isn't defined, but __loongarch__ is or the error on line 39 would trigger first
I see both of them in https://loongson.github.io/LoongArch-Documentation/LoongArch-toolchain-conventions-EN.html but don't know where they're supposed to come from | 12:08:15 |
 Puna | the compiler defines them based on the selected/configured target | 12:12:39 |
| Puna | https://github.com/gcc-mirror/gcc/blob/9a2402ad31db7507cb63905a8d98ce81769d9835/gcc/config/loongarch/loongarch-c.cc#L50-L56 | 12:13:18 |
| alexfmpe | so in this case GHC? or the c compiler? | 12:13:19 |
| Puna | well, whichever compiler is processing that file ig | 12:13:45 |
| alexfmpe | hmm the actual failing command seems to be gcc | 12:15:39 |
| alexfmpe | oh wait a second it does hit the line 39 error | 12:37:06 |
| alexfmpe | both errors show up actually | 12:37:19 |
| alexfmpe | so maybe ghc isn't configuring gcc properly for loongarch? | 12:37:33 |
| 11 Jan 2026 |
|  ivan joined the room. | 01:44:54 |
|  lukas joined the room. | 03:02:23 |
|  ghpzin changed their display name from ghpzin (moved to @ghpzin:envs.net) to ghpzin. | 15:04:40 |
|  @ghpzin:envs.net left the room. | 16:21:10 |
| 12 Jan 2026 |
|  jimmie joined the room. | 08:05:53 |
| jimmie set a profile picture. | 08:12:16 |
| jimmie changed their display name from zigzen to jimmie. | 08:12:34 |
|  jappie joined the room. | 17:28:20 |
| 13 Jan 2026 |
|  jopejoe1 (4094@epvpn) changed their display name from jopejoe1 (4094@39c3) to jopejoe1 (4094@epvpn). | 08:24:56 |
| 14 Jan 2026 |
|  BPub changed their display name from Robert to BPub. | 18:49:26 |
| 16 Jan 2026 |
|  keiwop joined the room. | 12:43:55 |
|  neobrain joined the room. | 13:41:20 |
| 17 Jan 2026 |
 Theo Paris | Is there a reason nixpkgs only has cctools for darwin, and not linux hosts? I need cctools-port to be able to cross compile pongoOS 🙃 | 22:35:53 |
| Theo Paris | * Is there a reason nixpkgs only has cctools for darwin, and not linux hosts? I need cctools-port to be able to cross compile pongoOS 🙃
Attempting to build it with --impure results in missing macos headers | 22:36:37 |
 emily | Darwin cross doesn't work in general right now. our ld64 patch set is incompatible with cctools-port and the latter was lagging far behind at the time we switched to our patches | 22:38:24 |
| emily | IIRC cctools-port patches are kind of crufty in various ways too. | 22:39:13 |
| 18 Jan 2026 |
 Randy Eckenrode | cctools-port doesn’t support LTO and does code signing in a weird way. | 19:55:24 |
| Randy Eckenrode | (Or, rather, LTO is broken.) | 19:55:34 |
