From: Timothy Sample <samplet@ngyro.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39699@debbugs.gnu.org
Subject: bug#39699: [core-updates] gash-boot0 fails on i686-linux
Date: Fri, 21 Feb 2020 09:18:55 -0500 [thread overview]
Message-ID: <878skwkoq8.fsf@ngyro.com> (raw)
In-Reply-To: <87zhdc9b1e.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 20 Feb 2020 22:57:49 +0100")
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> Marius Bakke <mbakke@fastmail.com> skribis:
>
>> Bootstrap fails early on i686-linux when trying to build gash-boot0,
>> which fails thusly:
>
> [...]
>
>> ?: 1 [primitive-load-path "compression/bzip2" ...]
>> In compression/bzip2.scm:
>> 45: 0 [#<procedure 8499a10 ()>]
>>
>> compression/bzip2.scm:45:18: In procedure #<procedure 8499a10 ()>:
>> compression/bzip2.scm:45:18: ERROR: R6RS exception:
>> 1. &error
>> 2. &who: bzip2
>> 3. &message: "This module requires at least 32-bit fixnums"
>> 4. &irritants: ()
>> command "tar" "xvf" "/gnu/store/bspn36jhcd2ky6ih7wnh9z0iz867flc2-gash-0.2.0.tar.gz" failed with status 1
>
> The error comes from the (compression bzip2) module included in
> “bootar”.
>
> I can see two solutions:
>
> 1. Remove bzip2 support from bootar (it’s not actually needed, is it?).
>
> 2. Modify (compression bzip2) so that it errors out on first use
> rather than at load time.
>
> Timothy, janneke, WDYT?
Both of those are good options. The 32-bit fixnum limit is a something
of a development artifact. I think I can remove it without problems.
If not, I will just remove BZip2 support for now, since I think you’re
right that we don’t use it.
Sorry for the little hiccup!
-- Tim
prev parent reply other threads:[~2020-02-21 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 17:24 bug#39699: [core-updates] gash-boot0 fails on i686-linux Marius Bakke
2020-02-20 21:57 ` Ludovic Courtès
2020-02-21 14:11 ` Jan Nieuwenhuizen
2020-02-21 20:38 ` Ludovic Courtès
2020-02-21 21:30 ` Jan Nieuwenhuizen
2020-02-21 23:28 ` Ludovic Courtès
2020-02-21 21:30 ` Jan Nieuwenhuizen
2020-02-22 5:07 ` Timothy Sample
2020-02-22 20:41 ` Ludovic Courtès
2020-02-21 14:18 ` Timothy Sample [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878skwkoq8.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=39699@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).