From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: 31/31: DRAFT gnu: bootstrap: Add support for the Hurd.
Date: Sun, 15 Mar 2020 19:23:52 +0100
Message-ID: <87o8sxiiiv.fsf@gnu.org>
References: <20200312065852.10633.59398@vcs0.savannah.gnu.org>
 <20200312065911.D981520B7E@vcs0.savannah.gnu.org>
 <874kuuvt9m.fsf@gnu.org> <87eetxrjtv.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:50194)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <janneke@gnu.org>) id 1jDXvb-0002EO-DR
 for guix-devel@gnu.org; Sun, 15 Mar 2020 14:24:00 -0400
In-Reply-To: <87eetxrjtv.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Thu, 12
 Mar 2020 10:41:48 +0100")
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org, 40006@debbugs.gnu.org

Jan Nieuwenhuizen writes:

>> For the sake of reducing complexity and keeping supported systems as
>> close to one another as possible, would it be an option to keep using
>> 2.0 for GNU/Hurd, like on the other systems?
...
>> That would entail changing make-bootstrap.scm to use 2.0 instead of 2.2
>> as a first step.  And yeah, it=E2=80=99d also entail another full rebuil=
d, which
>> I=E2=80=99m sorry for, but I think this kind of simplification pays off =
quickly.
>>
>> WDYT?
>
> Yes, let's do that.  I'll also want to look at using gcc-5, that may
> solve our libstdc++-boot0/gcc-boot0 problem.  I think it's weird that we
> build gcc-7 by default as bootstrap binary, while using that may not
> even work (and is certainly untested).

Yes; that worked and it simplifies things a lot.  So, wip-hurd is using
guile-2 and gcc-5 now.  Using gcc-5 allowed me to remove the puzzling
gcc-boot0 patch.

Just reset wip-hurd again; it was fully up to date with core-utils when
I started building the bootstrap-tarballs... Rebasing right now to
verify for a new round ;-)

Greetings,
janneke

--=20
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com