From: Christoph Buck <buck.christoph@googlemail.com>
To: help-guix@gnu.org
Subject: Cross platform deploy
Date: Mon, 08 Apr 2024 18:00:17 +0200 [thread overview]
Message-ID: <82r0ffj14e.fsf@googlemail.com> (raw)
Hi!
I have a quick question if the following is currently possible with the
latest version of guix.
I managed to cross-compile an `aarch64-linux-gnu` images (for the rpi4 in
case this matters) from my `x86_64-linux-gnu` host using
> guix system image --target=aarch64-linux-gnu my-image.scm --no-grafts --skip-checks
(Side note: Looks like i ran into the bug described in
https://issues.guix.gnu.org/66866 because i need the option
`--no-grafts` to sucessfully build the image).
This image boots successfully on my arm board. Now i want to remote
deploy system configurations from my `x86_64-linux-gnu` host. I setup
`guix deploy` using the following configuration
> (define machines
> (list (machine
> (operating-system rpi4-os)
> (environment managed-host-environment-type)
> (configuration (machine-ssh-configuration
> (host-name "pi4")
> (system "aarch64-linux")
> (user "root")
> (build-locally? #t)
> (port 2222))))))
where rpi4-os is my os configuration for my arm/rpi board.
To deploy changes I use
> guix deploy --no-grafts raspberry-pi.scm
After struggling for a bit to setup `qemu-binfmt`, this also seems to
work. However, instead of the cross-compiled kernel which should already
be in store, `guix deploy` recompiles the kernel using
`qemu-aarch64-static` emulation. This takes ages on my machine.
Is there a way to teach `guix deploy` to use the cross-compiled
packages? Unfortunately there seems to be no command line switch
`--target=xxx` which is present for `guix build` and `guix system`
Thanks in advance
Christoph
reply other threads:[~2024-04-09 9:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82r0ffj14e.fsf@googlemail.com \
--to=buck.christoph@googlemail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).