| 12 Jul 2024 |
 John Ericson | dramforever: oh that's a good point, yes it should be made to work | 13:12:30 |
| John Ericson | artemist: Yeah if that still exists, it's not hard to fix, and I think it might not | 13:13:02 |
| John Ericson | trofi: I agree, but in the case of GCC I think that is an especially frustrating package in the current state :) hopefully others will be better | 13:13:57 |
 trofi | all separateDebugInfo = true; packages (like glibc) are also affected as they encode into binary a checksum of debug sections in .debug.link section, those almost always contain $out :) | 14:24:47 |
| trofi | And I think ./configure almost never generates identical config.h for cross vs native due to inability to test runtime features (like iconv() runtime bugs in gnulib) | 14:26:52 |
| trofi | It's a fun exercise to attempt identical binary output for cross-vs-native, but it's very hard even for x86_64-linux-on-x86_64-linux case :) | 14:27:51 |
 Mindavi | In reply to @trofi:matrix.org
all separateDebugInfo = true; packages (like glibc) are also affected as they encode into binary a checksum of debug sections in .debug.link section, those almost always contain $out :) Looked into that again yesterday but couldn't find a solution yet :( | 14:57:20 |
| trofi | There probably is no simple solution. -ggdb2 vs -ggdb3 are expected to produce different debug infos even if binaries are identical otherwise. I personally disable separateDebugInfo locally (and use --build-id=none while at it as it has identical problem for CA derivations). | 15:04:36 |
| Mindavi | Locally I also do some hacks, but would still love to fix it upstream somehow | 15:09:59 |
| 13 Jul 2024 |
|  jopejoe1 joined the room. | 10:17:56 |
| 14 Jul 2024 |
|  tewi 🏳️⚧️ joined the room. | 16:38:15 |
|  Lan Tian joined the room. | 22:19:04 |
| 15 Jul 2024 |
|  dminca changed their display name from dminca to nixpkgs. | 17:28:48 |
| dminca changed their display name from nixpkgs to dminca. | 17:42:26 |
| tewi 🏳️⚧️ changed their display name from tewi to tewi 🏳️⚧️. | 20:45:56 |
| 16 Jul 2024 |
| tewi 🏳️⚧️ changed their profile picture. | 07:25:35 |
|  Marius changed their display name from Burrito (Marius) to Marius. | 12:16:17 |
 bl0v3 | 
Download image.png | 21:20:24 |
| bl0v3 | currently packaging zipl the s390x / Z mainframe bootloader | 21:21:08 |
| bl0v3 | but i wonder, since zipl only compiles for s390x <not x86> like the makefile ibm wrote intentionally refuses to build useful stuff for x86 ... | 21:22:39 |
| bl0v3 | would i even get this merged into nixpkgs since it supports neither x86 nor arm | 21:22:59 |
| bl0v3 | this matters because in order to write a bootloader module one needs s390x | 21:24:16 |
| bl0v3 | * this matters because in order to write a bootloader module one needs zipl | 21:24:26 |
| bl0v3 | uboot seems to be present for x86 but also there is ubootQemuRiscv64Smode in nixpkgs | 21:26:18 |
| bl0v3 | does that mean that non supported architecture packages can make their way into nixpkgs? | 21:26:41 |
| bl0v3 | my question is: can I get a package that only compiles for s390x yet cross compiles on x86 into nixpkgs? As in if the outputs of the drv are native to s390x but can be build on x86 will I get that into nixpkgs?
since i need s390x-tools for zipl which i need for creating what grub does for nixos | 21:31:24 |
| bl0v3 | * my question is: can I get a package that only compiles for s390x yet cross compiles on x86 into nixpkgs? As in if the outputs of the drv are native to s390x but can be build on x86 will I get that into nixpkgs?
since i need s390x-tools for zipl which i need for creating what grub does on x86 nixos | 21:31:35 |
| bl0v3 | seems like I can get it into nixpkgs | 22:13:59 |
| 17 Jul 2024 |
 dramforever | In reply to @bl0v3:matrix.org
my question is: can I get a package that only compiles for s390x yet cross compiles on x86 into nixpkgs? As in if the outputs of the drv are native to s390x but can be build on x86 will I get that into nixpkgs?
since i need s390x-tools for zipl which i need for creating what grub does on x86 nixos yes feel free to do so, just set meta.platforms to whatever s390x is | 05:26:18 |
| dramforever | also nice username | 05:26:22 |
