all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>,
	Timothy Sample <samplet@ngyro.com>,
	Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 39699@debbugs.gnu.org
Subject: bug#39699: [core-updates] gash-boot0 fails on i686-linux
Date: Thu, 20 Feb 2020 22:57:49 +0100	[thread overview]
Message-ID: <87zhdc9b1e.fsf@gnu.org> (raw)
In-Reply-To: <87y2sx41f2.fsf@devup.no> (Marius Bakke's message of "Thu, 20 Feb 2020 18:24:33 +0100")

Hi,

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?

Thanks,
Ludo’.

  reply	other threads:[~2020-02-20 21:58 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 [this message]
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

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=87zhdc9b1e.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39699@debbugs.gnu.org \
    --cc=janneke@gnu.org \
    --cc=mbakke@fastmail.com \
    --cc=samplet@ngyro.com \
    /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.