| 1 Mar 2024 |
 infinisil | In reply to @johannes.kirschbauer:scs.ems.host
Maybe yes. I think this could help speed up the rfc migration. Just gave you access. I'd still like to review PRs, but if I'm not responsive or you think it's not worth reviewing feel free to merge yourself :) | 03:07:37 |
 @johannes.kirschbauer:scs.ems.host | just having fun today: using "nix#nix-clangStdenv" i get sigSEV (segmentation fault). But using "nix#nix" is fine no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository. | 11:25:43 |
| @johannes.kirschbauer:scs.ems.host | * just having fun today: using "nix#nix-clangStdenv" i get SIGSEGV (Address boundary error). But using "nix#nix" is fine.. no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository. | 11:26:27 |
| @johannes.kirschbauer:scs.ems.host | * just having fun today: using "nix#nix-clangStdenv" i get SIGSEGV (Address boundary error). But using "nix#nix" is fine.. no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository.
Apart from that i would expect either both or none of the outputs to have segfaults. | 11:27:02 |
| @johannes.kirschbauer:scs.ems.host | * just having fun today: using "nix#nix-clangStdenv" i get SIGSEGV (Address boundary error). But using "nix#nix" is fine.. no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository.
Apart from that i would expect either both or none of the outputs to have segfault. | 11:27:13 |
| @johannes.kirschbauer:scs.ems.host | Some background, currently i patch nix before using it. It seems my patch spontaneously produces segfaults with clangStdenv only. | 11:29:38 |
| @johannes.kirschbauer:scs.ems.host | * Some background, currently i use a patched nix. It seems my patch spontaneously produces segfaults with clangStdenv only. | 11:30:02 |
| @johannes.kirschbauer:scs.ems.host | * Some background, currently i use a patched nix. It seems my patch spontaneously produces segfaults with clangStdenv only.
Q: why is the nix build system not reproducible ^^ | 11:30:30 |
| @johannes.kirschbauer:scs.ems.host | * Some background, currently i use a patched nix. It seems my patch spontaneously produces segfaults with clangStdenv only.
Q: why is the nix build system not reproducible ^^ (i mean it is, but wtf) | 11:30:59 |
| @johannes.kirschbauer:scs.ems.host | * Some background, currently i use a patched nix. It seems my patch spontaneously produces segfaults with clangStdenv only.
Q: why is the nix build system not reproducible ^^ | 11:31:17 |
| @johannes.kirschbauer:scs.ems.host | * Some background, currently i use a patched nix. It seems my patch spontaneously produces segfaults with clangStdenv only.
Q: why is the build of nix itself not reproducible ^^ | 11:31:41 |
| @johannes.kirschbauer:scs.ems.host | * Some background, currently i want to build a patched nix. It seems my patch spontaneously produces segfaults with clangStdenv only.
Q: why is the build of nix itself not reproducible ^^ | 11:35:05 |
|  tomberek set a profile picture. | 15:21:19 |
 Marc Jakobi | Download Vollmacht_fuer_Paketabholung.pdf | 19:10:38 |
 @jade_:matrix.org | In reply to @johannes.kirschbauer:scs.ems.host
just having fun today: using "nix#nix-clangStdenv" i get SIGSEGV (Address boundary error). But using "nix#nix" is fine.. no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository.
Apart from that i would expect either both or none of the outputs to have segfault. gcc vs clang build | 19:17:24 |
| @jade_:matrix.org | segv doesn't tell you anything, please coredumpctl debug if this is Linux and give the back trace (type bt into gdb) | 19:18:08 |
| @jade_:matrix.org | thank you | 19:18:11 |
 Alyssa Ross | C++ is not ABI-compatible between GCC and Clang, so you can't build some things with GCC, some with Clang, and then link them together. | 19:19:04 |
| Alyssa Ross | If you override Nix to build with Clang, boost will still be built with GCC | 19:19:14 |
| Alyssa Ross | So it's not expected to work. | 19:19:29 |
| Alyssa Ross | If the Nix flake is doing this, it should stop. | 19:20:17 |
| Alyssa Ross | ah, but it looks like it actually overrides stdenv in an overlay, so I guess that should work? | 19:21:10 |
| Alyssa Ross | It's very hard to read | 19:21:12 |
