From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 40839@debbugs.gnu.org
Subject: bug#40839: Shepherd activation .GO files are not cross-compiled ... and the Hurd
Date: Sat, 25 Apr 2020 14:32:14 +0200 [thread overview]
Message-ID: <87sggru4oh.fsf@gmail.com> (raw)
In-Reply-To: <87imhnuc8a.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Sat, 25 Apr 2020 11:49:09 +0200")
> The wip-hurd-vm branch cross-builds a VM for the Hurd. It uses some
> dedicated hacks to build the system packages, services, system profile
> and shepherd configuration and cross-build them into a qemu image.
>
> We did this to avoid too much struggle up front with parameterizing,
> working around, or removing Linux-specifics from "guix system
> --target=i586-pc-gnu build,vm,..."
I have not followed really closely the recent progress on the Hurd, but
I think we may need to synchronize at some point :)
As you have noticed our image creation is very tied to Linux and Intel
x86 compatible machines. I would like in the future that producing images
for other architectures/kernels could be less hacky.
My idea is to:
* Speed up image creation by removing the need to use VM to produce
images.
* Augment the operating-system record, or provide a new record, that
encapsulates information related to image layout (partitions,
bootloader location), target architecture (i586-pc-gnu,
aarch64-linux, ...).
This way, one would just have to run `guix system disk-image
my-board.scm' or `guix system disk-image --board=xxx config.scm', and
not have to worry about specifying the correct target triplet, kernel
and bootloader packages.
On the wip-disk-image, I propose the creation of an "image" record in
(gnu image), but I'm still not sure how to interface it.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-04-25 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 9:49 bug#40839: Shepherd activation .GO files are not cross-compiled ... and the Hurd Jan Nieuwenhuizen
2020-04-25 12:13 ` Mathieu Othacehe
2020-04-25 13:28 ` Jan Nieuwenhuizen
2020-04-25 15:53 ` Ludovic Courtès
2020-04-25 17:38 ` Jan Nieuwenhuizen
2020-05-02 13:15 ` Ludovic Courtès
2020-04-25 12:32 ` Mathieu Othacehe [this message]
2020-04-25 17:59 ` Jan Nieuwenhuizen
2020-04-27 12:35 ` Mathieu Othacehe
2020-04-28 17:20 ` Jan Nieuwenhuizen
2020-04-29 8:48 ` Mathieu Othacehe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sggru4oh.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=40839@debbugs.gnu.org \
--cc=janneke@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.