But I'd like to build the latest (19.03, I guess -- 18.09 still warns that cross-compiling for sd-image-aarch64 isn't possible)
This is the one-liner I have so far with a local `release-19.03` checkout in nixpkgs (but it doesn't seem to actually be cross-compiling?): `nix-build -I nixpkgs=nixpkgs/nixos -I nixos-config=nixpkgs/nixos/modules/installer/cd-dvd/sd-image-aarch64.nix nixpkgs/nixos --arg crossSystem '(import nixpkgs/lib/systems/examples).aarch64-multiplatform' -A config.system.build.sdImage`
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 255 seconds]
paulreimer has quit [Ping timeout: 256 seconds]
paulreimer - I'd strongly suggest you just do a local compile - I think the issue is that some of the infrastructure that generates the sd image doesn't do the right thing when cross compiling.
paulreimer has joined #nixos-aarch64
orivej has quit [Ping timeout: 268 seconds]
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
With qemu-user you can "natively" compile for aarch64 with your x86_64 dev machine
I've used that to get an aarch64 SD-image for my pinebook
(Mixed with cross-compiled packages whenever possible for speed)
jtojnar has joined #nixos-aarch64
oh crap, my connection had crapped out between my original post and 12:42 PST. If anyone posted anything before then, sorry but I didn't capture the history!
tilpner: hmmm, I was rather hoping for native cross-compilation performance (I have much faster x86_64 build machines on hand than my target). also, how did that 18.03 (raspberryPi) build accomplish it?
paulreimer: the cross-nixos-aarch64 repo should still work afaik, just build it against nixos-unstable instead of fork
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sorry does seem broken. you could try to bisect which commit breaks it (it used to work)
samueldr: thanks, that's handy. I did miss something, and caught it thanks to that!
grw: ah, I hoped it would be getting better! (release-18.09 had different errors, seemed less likely to work.) but maybe as you suggest, I should be looking to bisect between release-18.03..release-18.09.
anyway, sounds like it isn't going to work out-of-the-box... yet