unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Paul Boddie <paul@boddie.org.uk>
Cc: guix-devel@gnu.org
Subject: Re: Cross-building GuixSD (and maybe using pre-built toolchains)
Date: Tue, 5 Jul 2016 11:10:42 +0300	[thread overview]
Message-ID: <20160705081042.GC6523@debian-netbook> (raw)
In-Reply-To: <201607031651.28051.paul@boddie.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]

On Sun, Jul 03, 2016 at 04:51:27PM +0200, Paul Boddie wrote:
> Hello,
> 
...
>
> One thing that looks very promising is the ability to cross-bootstrap the 
> system, and I did manage to get that started for a new architecture (mipsel) 
> by performing some modifications suggested in the documentation [1], running 
> guix-daemon with the --disable-chroot flag, and then running this:
> 
> guix build --target=mipsel-linux-gnu bootstrap-tarballs
> 
> However, not wanting to leave my computer switched on all night, I stopped the 
> build after a while. I can understand the need to bootstrap things like 
> toolchains, but given that I am running Debian which has cross-toolchains for 
> mipsel, I wondered if I could short-circuit this process by employing pre-
> built toolchains. Would this be possible?

I built a set of bootstrap-tarballs on my very underpowered laptop
which took about 15 hours. The longest single package was gcc-4.9, which
took me about 5 hours. On a more powerful machine it should go much
faster.

> Finally, it seems to be the case that the workflow involves building a 
> bootstrapped minimal system and then natively building packages. Or have I 
> misunderstood the process? Is it possible to cross-build all of the packages 
> in the distribution?
> 
> I hope I haven't missed anything that tells me the answers to all of these 
> questions.
> 
> Thanks in advance for any answers you may have!
> 
> Paul
> 
> [1] https://www.gnu.org/software/guix/manual/html_node/Porting.html#Porting
> 

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-07-05  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-03 14:51 Cross-building GuixSD (and maybe using pre-built toolchains) Paul Boddie
2016-07-04 13:48 ` Ludovic Courtès
2016-07-05  8:10 ` Efraim Flashner [this message]

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=20160705081042.GC6523@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@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.
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).