From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Preparing the reduced bootstrap tarballs
Date: Thu, 15 Nov 2018 10:06:06 +0100
Message-ID: <87muqa4sn5.fsf_-_@gnu.org>
References: <20181014085857.3863-1-janneke@gnu.org>
	<20181014085857.3863-3-janneke@gnu.org> <87r2gld3nt.fsf@gnu.org>
	<875zxxax4f.fsf@gnu.org> <87sh0z6m83.fsf@gnu.org>
	<87ftwz9e9y.fsf@gnu.org> <874ldccr9f.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.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60039)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1gNDbN-0006XO-12
	for guix-devel@gnu.org; Thu, 15 Nov 2018 04:06:17 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1gNDbL-0007v3-Of
	for guix-devel@gnu.org; Thu, 15 Nov 2018 04:06:16 -0500
In-Reply-To: <874ldccr9f.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 23
	Oct 2018 23:00:44 +0200")
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: <http://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.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org

Hello!

(This is a followup to <https://bugs.gnu.org/33038>.)

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> Did those, pushed to core-updates-next as
>
>     d0bb7ed61ed9e356c53de1a8e9bd6c2ec030ffb6
>     doc: Update Preparing to Use the Bootstrap Binaries.

[...]

> I think that I'm "done" here, there's the `put new bootstrap binaries on
> ftp.gnu.org/pub/guix/...', are you taking care of that?

I (finally!) run =E2=80=9Cguix build bootstrap-tarballs=E2=80=9D on =E2=80=
=98core-updates-next=E2=80=99,
but that was a bit silly of me since that built the x86_64-linux
tarballs=E2=80=94i.e., not the =E2=80=9Creduced seed.=E2=80=9D

So I was about to re-run it with =E2=80=9C-s i686-linux=E2=80=9D, but I not=
iced the
following issue in (gnu packages make-bootstrap):

--8<---------------cut here---------------start------------->8---
(define %bootstrap-tarballs
  ;; A single derivation containing all the bootstrap tarballs, for
  ;; convenience.
  (package

[...]

    (inputs `(("guile-tarball" ,%guile-bootstrap-tarball)
              ,@(match (%current-system)
                  ("i686-linux" `(("mescc-tools-seed" ,(@ (gnu packages boo=
tstrap) %mescc-tools-seed))
                                  ("mes-seed" ,(@ (gnu packages bootstrap) =
%mes-seed))
                                  ("srfi-43" ,(@ (gnu packages bootstrap) %=
srfi-43))
                                  ("tinycc-seed" ,(@ (gnu packages bootstra=
p) %tinycc-seed))))
--8<---------------cut here---------------end--------------->8---

This does not actually build the bootstrap tarballs; instead it returns
the pre-built seeds (also the =E2=80=98%tinycc-seed=E2=80=99 variable doesn=
=E2=80=99t exist.)

What we would need here is something to build the things listed in
=E2=80=98%bootstrap-inputs=E2=80=99, namely:
=E2=80=98linux-libre-headers-stripped-4.14.26-i686-linux.tar.xz=E2=80=99 (e=
asy :-)),
=E2=80=98mescc-tools-seed-XYZ.tar.gz=E2=80=99, and
=E2=80=98mes-stripped-0.18-0.08f04f5-i686-linux.tar.xz=E2=80=99 (do we real=
ly need an
x86_64 version of this Mes?).

Does that make sense?

Sorry for the delay, and apologies if I overlooked something!

Ludo=E2=80=99.