"Tanguy Le Carrour" <[email protected]> writes: > Hi Guix, > > Since "my" recent success on installing Guix System on my Olimex Olinuxino > LIME2 [1], > I’ve been trying –"struggling with" would be more correct! 😅– different ways > to work > on improving the image and changing the system configuration on the board. > > [1]: https://codeberg.org/guix/guix/pulls/4960 > > Here are the options that I tried, chronologically: > > - install from a USB stick… FAILED > - cross-install from a running ARMbian… FAILED > - cross-compile* from my old D8… SLOW… FAILED > - cross-compile* from a bigger computer… SLOW… SUCCESS
You have made it much further than I! I use Guix to deploy a software stack to a Zynq7000 but I have not been successful in building an image with Guix (can't even get it to boot!) My process these days is guix pack --target with an install script which symlinks sysv init scripts and etc config files into the proper places on top of the yocto produced base system. It's not pretty but at least it gives me some "sane" method of updating/reproducing software without using yocto. Building the system image and using Guix deploy has been a pet project of mine for the last 5 years or so with very little success... > So I decided that I would give `guix deploy` a try. I would keep > cross-building > everything on my computer(s) and push only the store items to the > board and reconfigure. > It sounds like a great plan! 😎 But the question is… am I being > delusional?! 😅 This is the way! But I have never made it work. You might also try setting up your host machine as an offload build machine for the target although I'm not sure if that will work with cross compiling (perhaps with qemu-binfmt-service-type you can lie and say your host machine is aarch64). I had some small success with this with my pinebook before I bricked it. -- Mitchell Schmeisser OpenPGP Fingerprint: 089F 0E56 0087 9656 C463 691A 3811 C00D C428 5E27
