| 21 Oct 2021 |
 sterni | I may have to dive into this business now; I haven't dived into that topic to much so far, so I was kind of hoping for you answering here bc you are a lot more knowledgeable than me here | 10:15:12 |
| 22 Oct 2021 |
| sterni | trofi: btw https://github.com/NixOS/nixpkgs/pull/87909 | 09:09:19 |
| 25 Oct 2021 |
| sterni | I think this came up here: https://github.com/NixOS/nixpkgs/issues/142901 | 22:06:59 |
| 26 Oct 2021 |
|  @grahamc:nixos.orgchanged room power levels. | 01:16:31 |
|  NixOS Moderation Bot changed their display name from mjolnir to NixOS Moderation Bot. | 02:00:07 |
| NixOS Moderation Bot set a profile picture. | 02:00:25 |
| NixOS Moderation Bot changed their profile picture. | 02:23:38 |
| NixOS Moderation Bot changed their profile picture. | 02:33:08 |
| 27 Oct 2021 |
| sterni | Alyssa Ross: another “fun” fact: nixpkgs passes hostPlatform.config (a GNU triple) to the flag which at most understands LLVM triples + some hacks for certain things | 16:20:43 |
| sterni | :| | 16:20:44 |
| sterni | the problem is that we kind of need LLVM compat here because that's all Cabal understands, seemingly | 16:21:18 |
 trofi | I though Cabal uses GHC's notion of tuples which predates LLVM: https://gitlab.haskell.org/ghc/ghc/-/blob/master/m4/ghc_convert_cpu.m4#L3 (same for OS/VENDOR). | 20:03:45 |
| trofi | Also https://github.com/haskell/cabal/issues/5887 comes to mind | 20:05:15 |
| sterni | trofi: cabal can (attempt to) parse LLVM triples which was used in cabal | 21:38:10 |
| sterni | it ignores the vendor part completely I think | 21:38:27 |
| trofi | aha | 21:38:46 |
| sterni | also the things GHC and Cabal understand are slightly different | 21:39:04 |
| 10 May 2022 |
|  Piper McCorkle (they/them or she/her) changed their display name from Piper McCorkle (she/her or they/them) to Piper McCorkle (they/them or she/her). | 05:25:52 |
| 27 Oct 2021 |
| sterni | hence the GHC_CONVERT_{OS,CPU} macros | 21:39:13 |
| 29 Oct 2021 |
| sterni | John Ericson: any reason we are only building ghcHEAD in cross-trunk? I think this is the ghc version that works the worst atm | 10:31:22 |
| sterni | would probably make more sense to use the default version? | 10:31:38 |
|  @AleXoundOS:matrix.org joined the room. | 12:39:37 |
| @AleXoundOS:matrix.org | Hi. How can I use my own crosscompiler package (MIPS) instead of the one (GCC) from nixpkgs? | 14:36:33 |
 John Ericson | sterni: yeah that is probably a holdover from when only ghcHEAD worked, haha | 15:10:17 |
| John Ericson | good idea to change it | 15:10:23 |
| sterni | In reply to @AleXoundOS:matrix.org
Hi. How can I use my own crosscompiler package (MIPS) instead of the one (GCC) from nixpkgs? easiest is probably to package it properly and then use overrideCC stdenv buildPackages.my-cross-compiler as stdenv. | 17:25:24 |
| sterni | nixpkgs needs to be cross compiled correctly, so e. g. import <nixpkgs> { crossSystem = { config = "<your autoconf triple>"; }c | 17:27:01 |
| sterni | * nixpkgs needs to be cross compiled correctly, so e. g. import <nixpkgs> { crossSystem = { config = "<your autoconf triple>"; } | 17:27:03 |
| sterni | if you are targeting mips, I'm not sure how will nixpkgs will cope with that seems only mipsel is explored territory | 17:27:29 |
| sterni | John Ericson: oh we do ghcHEAD and default ghc | 17:57:05 |
