unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: bootstrap: i686-linux now builds without binutils, gcc seeds
Date: Wed, 19 Sep 2018 20:07:54 +0200	[thread overview]
Message-ID: <87efdpwebp.fsf@gnu.org> (raw)
In-Reply-To: <87tvmm13dj.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Wed, 19 Sep 2018 07:07:52 +0200")

Jan Nieuwenhuizen writes:

> Just to give you a heads up: four `Oops' fixup-commits later I decided
> to squash them again and create a fresh wip-bootstrap: d7feea557.
>
> I think it could be ready for a rename to core-updates-next.
>
> $ guix hash -r /gnu/store/y7wy6yr4j19f7d5xlqdln094nivy4cx3-hello-2.10
> 0ab0nazn6v0ybkig9xn58xjk4rqcyanp4wy4rywf32nyl8bgbly5

I finally realised what it really means that the GuixSD bootstrap has
`binutils-cross-boot0' (I really think that should be reflected in the
SCM name too?) and `gcc-cross-boot0': bolting the x86_64-linux bootstrap
onto the i686-linux Mes bootstrap proved to be "almost" trivial (very
low hanging fruit I think whas wat Ludovic said).

So, I took the freedom to add another commit onto wip-bootstrap that
also replaces the x86_64-linux bootstrap.  I realise that this commit
may have its own problems; so when moving to core-updates-next we may
want to be a bit careful before taking it in.

Greetings,
janneke

  reply	other threads:[~2018-09-19 18:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 16:31 bootstrap: i686-linux now builds without binutils, gcc seeds Jan Nieuwenhuizen
2018-09-01 18:16 ` Gábor Boskovits
2018-09-02  5:21   ` Jan Nieuwenhuizen
2018-09-16 19:24 ` Ludovic Courtès
2018-09-17  6:10   ` Pjotr Prins
2018-09-17 18:29   ` Ricardo Wurmus
2018-09-17 19:25     ` Jan Nieuwenhuizen
2018-09-17 19:47   ` Jan Nieuwenhuizen
2018-09-17 21:55     ` Ricardo Wurmus
2018-09-18  8:27       ` Jan Nieuwenhuizen
2018-09-18  8:04     ` Vincent Legoll
2018-09-18  8:33       ` Jan Nieuwenhuizen
2018-09-18 20:53     ` Jan Nieuwenhuizen
2018-09-19  5:07       ` Jan Nieuwenhuizen
2018-09-19 18:07         ` Jan Nieuwenhuizen [this message]
2018-09-22 12:35           ` Ludovic Courtès
2018-09-22 15:34             ` Jan Nieuwenhuizen
2018-09-22 18:23               ` Jan Nieuwenhuizen
2018-09-23  8:02                 ` branched core-updates-next [WAS: Re: bootstrap: i686-linux now builds without binutils, gcc seeds] Jan Nieuwenhuizen
2018-09-23 16:09               ` bootstrap: i686-linux now builds without binutils, gcc seeds Joshua Branson
2018-09-23 16:29                 ` Jonathan Brielmaier
2018-09-22 12:23     ` Ludovic Courtès
2018-09-22 14:38       ` Jan Nieuwenhuizen

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=87efdpwebp.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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).