Nix Cross Compiling | 581 Members | |
| 126 Servers |
| Sender | Message | Time |
|---|---|---|
| 11 Feb 2026 | ||
| the screenshot of boot menu is epic | 11:22:49 | |
| I am starting on the build | 11:23:01 | |
| trying to YOLO the cross compile. If that fails, I will move to a native build or try QEMU static | 12:04:06 | |
| https://github.com/NixOS/nixpkgs/issues/473862#issuecomment-3872075407 has a change to rust-bindgen which may get you further, if you fail on smth with
| 12:08:54 | |
| it stopped on GRUB:
It tried to generate fonts and got confused between host and cross system it seems. No worries, I will try it on a native system on the weekend | 17:06:23 | |
i feel like i had fixed that at some point when i tried to test grub2_ieee1275 built cross… | 17:28:03 | |
ah, i must've excluded that to get rid of 10.rebuild-nixos-tests… | 17:29:48 | |
| https://github.com/NixOS/nixpkgs/commit/5dd035f7ff49bf2ff560720e46d5505cd02e1367 try applying this | 17:30:37 | |
* ah, i must've excluded that to get rid of 10.rebuild-nixos-tests on the grub2_ieee1275 init, and then forgotten about submitting that separately… | 17:37:15 | |
| applied, and re-trying | 17:59:03 | |
building the BootX with the fancy nixos flake icon cross fails. moving ppm2osbadgeicon from the let block into pkgs/by-name/pm/ppm2osbadgeicons so it doesn't try to run a cross-compiled binary should fix it… | 18:17:28 | |
| 12 Feb 2026 | ||
| it did not get that far yet. Cross compiling libqrtr fails:
any direction I should look at? I am clsoe to finishing the installer cross compile | 07:58:27 | |
| this one has some special logic for meson cross-compile: | 08:28:03 | |
| it tried to use the following qemu wrapper: | 09:58:36 | |
| and seems it passed some ppc64 binaries in the LD_ paths I think | 09:58:56 | |
| qemu-ppc64 seems to work fine, it is my host native binary | 09:59:42 | |
| 10:20:22 | ||
| hi, can someone take a look at https://github.com/NixOS/nixpkgs/pull/489743 please? it does fix one issue for fractal to crosscompile but i am not sure if this is the most elegant way to solve it | 11:36:24 | |
| if I disable modemmanager, it fails on gdk-pixbuf: | 12:01:58 | |
| that sounds like something got linked incorrectly. built for the buildPlatform, but with hostPlatform library paths in its rpath. | 12:08:57 | |
| i'm failing in
| 12:42:07 | |
| i'll try to submit the grub thing from earlier when i have time (not rn) and i'll adjust the bootx stuff so cross is happier, but i don't have a clue for this one. you might have to setup either a VM or some other linux distro on the machine itself, build the image natively, and let the machine run for afew days… | 12:43:49 | |
| * i'll try to submit the grub thing from earlier when i have time (not rn) and i'll adjust the bootx stuff so cross is happier, but i don't have a clue for this one. you might have to setup either a VM or some other linux distro on the machine itself, start building the image natively, and let the machine run for afew days to complete the builds… | 12:44:23 | |
| (same error on nixpkgs master FWIW) | 12:45:51 | |
i think the issue is that we fix up the target triplet for clang by passing -target powerpc64-unknown-linux-gnu, but don't have a powerpc64-unknown-linux-gnu-ld in clangStdenv.cc.bintools. only a powerpc64-unknown-linux-gnuabielfv1-ld… guh | 13:29:26 | |
-fuse-ld=<full path to corresponding bintools wrapper>/bin/<original target>-ld works… anything against throwing this into the General clang support section somehow? | 13:44:39 | |
* -fuse-ld=<full path to corresponding bintools wrapper>/bin/<original target triplet>-ld works… anything against throwing this into the General clang support section somehow? | 13:44:49 | |
| "if doing cross cross and <new target triplet>-ld doesn't exist, add the above flag" | 13:45:26 | |
| or it might be time to look deeper into clang and figure out how to make it just accept our full triplets like GCC does, instead of requiring all this song-and-dance. but big scary code base… | 13:46:24 | |
| 20:33:44 | ||