GNU bug report logs - #26339
[PATCH 00/18] wip: Support non grub bootloaders.

Previous Next

Package: guix-patches;

Reported by: Mathieu Othacehe <m.othacehe <at> gmail.com>

Date: Sun, 2 Apr 2017 13:51:01 UTC

Severity: important

Tags: patch

Done: Mathieu Othacehe <m.othacehe <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: ludo <at> gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 26339 <at> debbugs.gnu.org
Subject: [bug#26339] closing bootloader serie.
Date: Thu, 26 Oct 2017 15:20:30 -0700
Mathieu Othacehe <m.othacehe <at> gmail.com> skribis:

>> That said, I experimented with cross-compiled GuixSD (that is, ‘guix
>> system build --target=foo-linux-gnu’), and I think that’s promising,
>> with the caveat that you have to restrict your package set to those that
>> can actually be cross-compiled.  Should we try to get it off the ground?
>
> That would be really interesting. But to build an arm GuixSD installer
> for example, it would require that are all the packages needed to set-up
> the rootfs of the installer are cross-compilable, right ?

Yes.  So in my experiments I had ‘services’ and ‘packages’ almost empty,
to be sure.

> What's the difference between --system=armhf-linux and
> --target=arm-linux-gnueabihf ?

‘--target’ specifies a cross-compilation triplet, where ‘--system’
specifies the system you want to build on.  Without offloading, your
x86_64 machine can only build for ‘x86_64-linux’ or ‘i686-linux’.

Conversely cross-compilation does not depend on offloading, it’s just
regular cross-compilation.

Does that make sense?

Ludo’.




This bug report was last modified 7 years and 209 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.