unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Paul Boddie <paul@boddie.org.uk>
Cc: help-guix@gnu.org
Subject: Re: Cross-building GuixSD (and maybe using pre-built toolchains)
Date: Thu, 01 Sep 2016 21:43:38 +0200	[thread overview]
Message-ID: <87twdzwglx.fsf@gnu.org> (raw)
In-Reply-To: <201609011751.42108.paul@boddie.org.uk> (Paul Boddie's message of "Thu, 1 Sep 2016 17:51:41 +0200")

Paul Boddie <paul@boddie.org.uk> skribis:

> When you write "cross-compile from x86_64" do you mean run a cross-compiler on 
> an x86_64 host that targets another architecture? (I'm guessing "yes".)

Yes.

> From previous questions, it appears that any compiler must have been built 
> specifically for Guix to use (and cannot be those those pre-built toolchains 
> provided by, say, Debian), so would these cross-compilers be the ones normally 
> used to generate the "bootstrap binaries" (that would normally be used to then 
> build packages on the target system)?

Yes, Guix packages only depend on other Guix packages; there cannot be
dependencies on external packages.

> Or do I first bootstrap Guix on my (x86_64, in this example) "build system", 
> then generate special cross-compilers for my target architecture (that are 
> then exposed via offloading)?

Offloading and cross-compilation are unrelated.  Offloading is just a
mechanism that allows distributed builds.

Guix supports x86_64-linux-gnu, so, IOW, the distro is already
“bootstrapped” for that platform.  There’s nothing special to be done.

I’m trying to find ways to rephrase this, but I can’t think of other
ways than what the “Bootstrapping” and “Porting” sections of the manuals
say.  :-)

> And can I provide a foreign architecture build daemon on the same machine as 
> the one performing the build?

No.

> Sorry if this is all obvious or if I'm not assuming that what is possible is 
> actually possible! I'm used to discovering limitations with build systems. (To 
> me it is remarkable that given all the portable things like shell scripts that 
> do a lot of the lifting in build processes, many build systems have an 
> unreasonable affinity to the build host's architecture.)
>
> Thanks for all the help!

No problem!  I realize it can be difficult to convey the big picture of
Guix here to someone already familiar with other build systems.

Ludo’.

  reply	other threads:[~2016-09-01 19:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 21:26 Cross-building GuixSD (and maybe using pre-built toolchains) Paul Boddie
2016-08-31 20:04 ` Ludovic Courtès
2016-08-31 21:49   ` Paul Boddie
2016-09-01  8:10     ` Ludovic Courtès
2016-09-01 15:51       ` Paul Boddie
2016-09-01 19:43         ` Ludovic Courtès [this message]
2016-09-02 18:52         ` David Craven
2016-09-03 12:56           ` Ludovic Courtès
2016-09-03 12:59             ` David Craven
2016-09-03 21:18               ` Ludovic Courtès
2016-09-03 21:27                 ` David Craven
  -- strict thread matches above, loose matches on Subject: below --
2016-08-31 16:15 David Craven
2016-08-31 20:08 ` Ludovic Courtès
2016-08-31 22:01   ` David Craven
2016-08-31 22:13     ` David Craven
2016-09-01  8:17     ` Ludovic Courtès
2016-09-01 10:11       ` David Craven
2016-09-01 11:16         ` Ludovic Courtès
2016-09-01 11:59       ` Ludovic Courtès

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=87twdzwglx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=paul@boddie.org.uk \
    /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).