guix-devel
[Top][All Lists]
Advanced

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

Preparing the reduced bootstrap tarballs


From: Ludovic Courtès
Subject: Preparing the reduced bootstrap tarballs
Date: Thu, 15 Nov 2018 10:06:06 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Hello!

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

Jan Nieuwenhuizen <address@hidden> 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 “guix build bootstrap-tarballs” on ‘core-updates-next’,
but that was a bit silly of me since that built the x86_64-linux
tarballs—i.e., not the “reduced seed.”

So I was about to re-run it with “-s i686-linux”, but I noticed 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 
bootstrap) %mescc-tools-seed))
                                  ("mes-seed" ,(@ (gnu packages bootstrap) 
%mes-seed))
                                  ("srfi-43" ,(@ (gnu packages bootstrap) 
%srfi-43))
                                  ("tinycc-seed" ,(@ (gnu packages bootstrap) 
%tinycc-seed))))
--8<---------------cut here---------------end--------------->8---

This does not actually build the bootstrap tarballs; instead it returns
the pre-built seeds (also the ‘%tinycc-seed’ variable doesn’t exist.)

What we would need here is something to build the things listed in
‘%bootstrap-inputs’, namely:
‘linux-libre-headers-stripped-4.14.26-i686-linux.tar.xz’ (easy :-)),
‘mescc-tools-seed-XYZ.tar.gz’, and
‘mes-stripped-0.18-0.08f04f5-i686-linux.tar.xz’ (do we really need an
x86_64 version of this Mes?).

Does that make sense?

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

Ludo’.



reply via email to

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