guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bootstrap: i686-linux now builds without binutils, gcc seeds


From: Ricardo Wurmus
Subject: Re: bootstrap: i686-linux now builds without binutils, gcc seeds
Date: Mon, 17 Sep 2018 20:29:40 +0200
User-agent: mu4e 1.0; emacs 26.1

Ludovic Courtès <address@hidden> writes:

> Hello Janneke!
>
> It’s taken me a while but I successfully built 
> /gnu/store/58q6748dydqxrhrw8xn2gsf60djl6gvv-hello-2.10
> for i686 from commit 5d8b7131c23d2285dd3546c59022dd5953508943 of
> ‘wip-bootstrap’.  :-)
>
> --8<---------------cut here---------------start------------->8---
> $ guix hash -r /gnu/store/58q6748dydqxrhrw8xn2gsf60djl6gvv-hello-2.10
> 005zi21nvhmygjam6vsvkgmw9awsmyacz6a65naxcblrpbra1g94
> --8<---------------cut here---------------end--------------->8---
>
> The “interesting commits” are these:
>
>   5d8b7131c * gnu: mes: Oops, use mirror://gnu download url.
>   1ff6d26ac * bootstrap: Replace GNU toolchain seeds with Mes for i686-linux.
>   ca8895bdb * bootstrap: Add Mes bootstrap.
>   be65bf958 * gnu: Add Mes bootstrap seeds.
>   45856f886 * gnu: Add linux-libre-headers-bootstrap-tarball.
>   cd9830fcd * guix: copy-linux-headers: Prepare for Mes bootstrap.
>   6265040e7 * guix: package-from-tarball: Allow PROGRAM-TO-TEST to be #f.
>   8d9c16ed3 * gnu: texinfo-boot0: Remove bootstrap leaks.
>   f9a76a79c * gnu: bison-boot0: Remove bootstrap leaks.
>   12394cc83 * gnu: m4-boot0: New variable.
>   6891da335 * gnu: perl-boot0: Remove bootstrap leaks.
>   f933b162c * gnu: file-boot0: Remove bootstrap leaks.
>   9c0912a20 * gnu: findutils-boot0: Remove bootstrap leaks.
>   53616d896 * gnu: diffutils-boot0: Remove bootstrap leaks.
>   7503cee76 * bootstrap: %bootstrap-inputs+toolchain: Prepare for Mes 
> bootstrap.
>   80bd4a995 * bootstrap: %bootstrap-inputs: Prepare for Mes bootstrap.
>
> I looked at the result and overall it LGTM!  So I think the next step is
> to rebase the branch on ‘core-updates’ (or merge it) and rename it
> ‘core-updates-next’.  WDYT?  Ricardo?

Using Janneke’s impressive work as the beginning of core-updates-next
sounds good to me.

I’m sorry I haven’t yet been able to review wip-bootstrap myself.

--
Ricardo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]