From: Manolis Ragkousis <manolis837@gmail.com>
To: Paul Boddie <paul@boddie.org.uk>, help-guix@gnu.org
Subject: Re: Bootstrapping on a new platform
Date: Sun, 3 Dec 2017 08:46:56 +0200 [thread overview]
Message-ID: <b59b4711-a3ed-ad76-9f3e-81e0ffcc4d30@gmail.com> (raw)
In-Reply-To: <201712030017.19982.paul@boddie.org.uk>
Hello Paul,
On 12/03/17 01:17, Paul Boddie wrote:
> I finally got round to trying to build Guix again, this time doing a native
> build rather than a cross-build. However, I'm attempting this on an
> unsupported platform (mipsel), and it isn't clear what I need to do to make
> the bootstrap binaries and thus attempt a source build.
>
> What I've figured out so far is this:
>
> tar zxf guix-0.13.0.tar.gz
> cd guix-0.13.0
> ./bootstrap
> ./configure --with-courage
> make
> make install
>
> This gets me the guix-daemon, but upon trying to do anything, I get the
> following:
>
> guix build: error: could not find bootstrap binary 'tar' for system 'mipsel-
> linux'
>
You need to cross-build those binaries from a system that is supported,
like x86_64-linux for example.
> I understand that I need some bootstrap binaries, and the bootstrapping
> documentation indicates that these can indeed be generated as follows:
>
> guix build --target=mipsel-linux-gnu bootstrap-tarballs
>
> But this just gives the same error. And I am actually running on mipsel-linux-
> gnu, so I suppose it might be different if I were try this on a supported
> system - i386-linux-gnu, for instance - and thus generate the binaries that
> way.
>
> Maybe I have just missed the part of the manual that talks about these source
> builds, but it really doesn't seem obvious to me. Another thing, which I've
> seen mentioned on this list is reproducible builds. Might it be possible to
> have architecture-independent source archives that reproducibly build the
> binaries?
>
First I would suggest checking out my talk in FOSDEM 17 which I tried to
explain how bootstrapping in Guix works, along with how I did it for
Hurd. [1]
The simplified steps are the following:
1) Cross-build those binaries from a supported system
2) Add the new binaries to Guix (check gnu/packages/bootstrap.scm)
3) Copy the Guix source which now has the new binaries to the system you
are trying to port it to. I suggest working on the git version of Guix
for this. It's good to have the updated version.
4) ./boostrap && ./configure --with-courage && make
5) work out issues and enjoy.
Does this make sense? I have spent a lot of time on this so please ask
and I can help you :).
Manolis
[1] https://archive.fosdem.org/2017/schedule/event/guixhurd/
next prev parent reply other threads:[~2017-12-03 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 23:17 Bootstrapping on a new platform Paul Boddie
2017-12-03 6:46 ` Manolis Ragkousis [this message]
2017-12-03 9:54 ` Efraim Flashner
2017-12-04 18:24 ` Paul Boddie
2017-12-08 10:28 ` Ludovic Courtès
2017-12-08 13:40 ` Paul Boddie
2017-12-08 16:19 ` Paul Boddie
2017-12-11 11:03 ` Ludovic Courtès
2017-12-11 16:36 ` Paul Boddie
2017-12-12 16:10 ` Ludovic Courtès
2017-12-12 16:29 ` Paul Boddie
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=b59b4711-a3ed-ad76-9f3e-81e0ffcc4d30@gmail.com \
--to=manolis837@gmail.com \
--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).