From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 40839@debbugs.gnu.org
Subject: bug#40839: Shepherd activation .GO files are not cross-compiled ... and the Hurd
Date: Sat, 25 Apr 2020 19:59:18 +0200 [thread overview]
Message-ID: <871robtpjd.fsf@gnu.org> (raw)
In-Reply-To: <87sggru4oh.fsf@gmail.com> (Mathieu Othacehe's message of "Sat, 25 Apr 2020 14:32:14 +0200")
Mathieu Othacehe writes:
>> 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 :)
Oh no! :)
I haven't been following either...but I did notice that "guix system
reconfigure" may be tricky on the Hurd, given that it does not have
Qemu. I was actively trying not to think about that, hoping some
solution would present itself.
> 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.
Yes...the Intel bit isn't really hurting the Hurd efforts yet (sadly),
but I see what you mean.
> 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 for the ping and the summary: I should really look into that!
I am currently still looking to consolidate all the cross build fixes,
and how to migrate the Shepherd and services hacks into the regular
framework. I'm guessing that's all stuff that wip-disk-image does not
touch/change.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-04-25 18:00 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
2020-04-25 17:59 ` Jan Nieuwenhuizen [this message]
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
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=871robtpjd.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=40839@debbugs.gnu.org \
--cc=m.othacehe@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).