all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guile 2.0 in make-bootstrap.scm
Date: Wed, 6 Jan 2021 11:04:43 +0200	[thread overview]
Message-ID: <X/V9KwY4jB/nFalB@3900XT> (raw)
In-Reply-To: <87zh1mqw10.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]

On Wed, Jan 06, 2021 at 10:01:15AM +0100, Ludovic Courtès wrote:
> Hi Janneke!
> 
> While uploading the powerpc64le-linux tarballs, I noticed they use Guile
> 2.0, which reminded me of eef44fea17a735d2f4048a747d16af478d4b9dbc:
> 
>     Revert "gnu: guile-static-stripped: Update to 2.2."
>     
>     As discussed on IRC, keeping bootstrap Guile on 2.0 simplifies adding new
>     architectures and removes the need for parameterizing
>     gnu/packages/bootstrap.scm.
>     
>     This reverts commit 2acfe022a740f79b593348cc6362cc4ee8f33bb4.
>     
>     * gnu/packages/make-bootstrap.scm (%guile-static): Revert to guile-2.0.  Retain
>     build recipe.
>     * gnu/packages/patches/guile-relocatable.patch: Update for Guile 2.0.14.
> 
> Do you remember the reason for this change?
> 
> What’s surprising is that
> <https://ftp.gnu.org/gnu/guix/bootstrap/i686-linux/20190815> does use
> 2.2.
> 

That wasn't me? (I apparently touch everything) I remember guile-2.2 for
the bootstrap had (likely) endianness ordering issues with PPC32, and it
was far simpler to revert back to guile-2.0 than to try to fix it.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-01-06  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06  9:01 Guile 2.0 in make-bootstrap.scm Ludovic Courtès
2021-01-06  9:04 ` Efraim Flashner [this message]
2021-01-06 11:01 ` Jan Nieuwenhuizen
2021-01-08 17:14   ` Timothy Sample

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=X/V9KwY4jB/nFalB@3900XT \
    --to=efraim@flashner.co.il \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.