| 6 Dec 2025 |
 matthewcroughan | for some reason this nghttp2 is failing in the case of native compilation? | 00:15:32 |
| matthewcroughan | * for some reason this nghttp2 is failing in the case of native compilation with exec format error? | 00:15:36 |
| matthewcroughan | any ideas? | 00:15:42 |
| matthewcroughan | musl-llvm native | 00:15:58 |
| matthewcroughan | * musl-llvm + native | 00:16:04 |
| matthewcroughan | * musl + llvm native | 00:16:08 |
 Artturin | In reply to @matthewcroughan:defenestrate.it
hercules-ci.com/accounts/github/MatthewCroughan/derivations/%2Fnix%2Fstore%2Fzgwfi5b3g9jz98l2dcgmyxmqwwixynh6-nghttp2-1.67.1.drv/log?via-job=fd45ac98-e62d-4090-9ae9-4161885e3a6e ./configure is likely a script, check it's shebang | 00:52:44 |
| matthewcroughan | But why would it work in all other cases than llvm native? | 00:54:21 |
| matthewcroughan | why would pkgsLLVM.stdenv not work whilst stdenv would? | 00:54:56 |
| Artturin | In reply to @matthewcroughan:defenestrate.it
But why would it work in all other cases than llvm native? Dunno, that's what were attempting to troubleshoot | 00:57:59 |
| Artturin | * Dunno, that's what we're attempting to troubleshoot | 00:58:11 |
| Artturin | Copy the path in the shebang and try to run it out of the build | 00:58:48 |
| Artturin | Check the interpreter path with readelf -l
Check file too
Try running it with strace | 01:09:01 |
| matthewcroughan | Artturin: Amazingly, it seems to have been an error on the nix daemon or scheduler somehow | 02:37:25 |
| matthewcroughan | or something inexplicable | 02:37:28 |
| matthewcroughan | I rebuilt everything, seems to have worked now | 02:37:40 |
| matthewcroughan | maybe it was some rare case that can happen in the build, a race or something with patching the configure script | 02:37:58 |
|  P J joined the room. | 07:43:21 |
| 7 Dec 2025 |
 Jaafar | Would cc be just the compiler or the whole toolchain (i.e. linker, libc++, etc.)? Because I'd like the latter.
I have something like this inside a libcxxStdenv.mkDerivation
buildInputs = [
pkgs.wineWow64Packages.stableFull
];
nativeBuildInputs = [
pkgs.pkgsCross.mingwW64.stdenv.cc
];
| 20:46:55 |
| Jaafar | * Would cc be just the compiler or the whole toolchain (i.e. linker, libc++, etc.)? Because I'd like the latter.
I have something like this inside a libcxxStdenv.mkDerivation
nativeBuildInputs = [
pkgs.pkgsCross.mingwW64.stdenv.cc
];
| 20:47:14 |
| Jaafar | * Would cc be just the compiler or the whole toolchain (i.e. linker, C++ standard library, etc.)? Because I'd like the latter.
I have something like this inside a libcxxStdenv.mkDerivation
nativeBuildInputs = [
pkgs.pkgsCross.mingwW64.stdenv.cc
];
| 20:47:39 |
| Artturin | depsBuildBuild = [ pkgsBuildBuild.stdenv.cc ];, usually done as buildPackages.stdenv.cc in nixpkgs for some reason
stdenv is special in the way that it comes from the previous stage
buildPackages = pkgsBuildHost
| 21:08:23 |
 dramforever | these are the same, fortunately | 21:09:12 |
| dramforever | i think | 21:09:32 |
| Artturin | They're the same | 21:09:41 |
| dramforever | yeah they're the same | 21:09:50 |
| Artturin | * depsBuildBuild = [ pkgsBuildBuild.stdenv.cc ];, usually done as buildPackages.stdenv.cc in nixpkgs for some reason
stdenv is special in the way that it comes from the previous stage so for it either of those 2 is fine
buildPackages = pkgsBuildHost
| 21:11:04 |
| Artturin | You can build stdenv.cc and see what's in it | 21:16:28 |
| Artturin | It has the hooks to add the required vars and populate them | 21:16:42 |
| Artturin | * It has the hooks to add the required vars and populate them for the wrapper | 21:16:54 |
