| 26 Sep 2025 |
 dramforever | pkgsLLVM.ncdu works on my branch | 12:44:02 |
| dramforever | 
Download Screenshot_20250926_204454.png | 12:45:04 |
| dramforever | matthewcroughan: did you do this? i didn't do that to everything on my branch because i didn't feel like fixing everything yet | 12:45:20 |
 matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | is ncdu using zig somehow? | 12:45:22 |
| dramforever | yes, ncdu is zig | 12:45:32 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | does zig itself use its own hooks? | 12:45:41 |
| dramforever | uses zig_0_15 | 12:45:49 |
| dramforever | it uses zig_0_15.hook, so needs to be either changed to pkgsBuildHost.zig_0_15.hook, or i'd have to splice zig_0_15.hook | 12:46:21 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | There's no way to do that for zig, because zig itself does not use its own hook? | 12:48:28 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | dramforever: I asked about it here, so maybe someone inside zig will know https://github.com/ziglang/zig/issues/25357 | 12:54:30 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | mm, for some reason audit tests fail on llvm/cross on staging | 14:23:53 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | * mm, for some reason audit tests fail on llvm/cross on staging-next | 14:23:55 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | diffutils-aarch64-linux> .. contents:: :depth: 2
diffutils-aarch64-linux>
diffutils-aarch64-linux> FAIL: test-c32ispunct.sh
diffutils-aarch64-linux> ========================
diffutils-aarch64-linux>
diffutils-aarch64-linux> test-c32ispunct.c:261: assertion 'is == 0' failed
diffutils-aarch64-linux> Aborted (core dumped)
diffutils-aarch64-linux> FAIL test-c32ispunct.sh (exit status: 1)
| 14:50:25 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | same for diffutils.. hmm | 14:50:28 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | https://patchwork.yoctoproject.org/project/oe-core/patch/20250819010128.3519760-3-raj.khem@gmail.com/ | 14:50:58 |
| 27 Sep 2025 |
 outfoxxed | I feel like this is wrong (it does work) but I don't know how I'm supposed to deal with it: | 20:20:52 |
| outfoxxed | 
Download image.png | 20:20:53 |
| outfoxxed | 
Download image.png | 20:21:23 |
| outfoxxed | If we have multiple host offsets then the hook separates build/target packages, otherwise it doesn't | 20:21:57 |
 K900 | I think the correct way to do Qt6 cross is to always have it be nativeBuildInputs | 20:24:50 |
| K900 | And dispatch on $target | 20:24:58 |
| outfoxxed | The qt packages themselves should potentially depend on their pkgsBuildHost versions in nativeBuildInputs | 20:26:31 |
| K900 | It's extremely stupid | 20:26:31 |
| outfoxxed | but users shouldnt have to | 20:26:33 |
| K900 | No, that's not what I meant | 20:26:41 |
| K900 | I mean that Qt cross is weird enough that we basically want to have Qt always be "on build for target" | 20:27:03 |
| outfoxxed | Yeah currently all the package files pass things via cmake flags to override paths which im not particularly fond of | 20:27:05 |
| K900 | And target-aware | 20:27:16 |
| outfoxxed | so far I've successfully crossed everything to riscv64 using the hook stuff above but I'm going to try removing all the special casing from the nix expressions and just hoping QT_ADDITIONAL_HOST_PACKAGES_PREFIX_PATH does what its supposed to | 20:28:11 |
 Alyssa Ross | Nice! | 20:28:26 |
