unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Streit <simon@netpanic.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 50212@debbugs.gnu.org
Subject: bug#50212: Several tests fail, Bash fails often. Was: Tests fail while building Guix
Date: Sun, 29 Aug 2021 00:32:25 +0200	[thread overview]
Message-ID: <yguy28lp5dy.fsf@netpanic.org> (raw)
In-Reply-To: <5fed54e119c256140ccfc15baa239947c988caef.camel@telenet.be> (Maxime Devos's message of "Sat, 28 Aug 2021 17:00:50 +0200")

Hello Maxime,

Maxime Devos <maximedevos@telenet.be> writes:
> Some questions:
>
> * What's the hash of gnu/packages/bootstrap/i686-linux/bash?
>
>   (Run guix hash gnu/packages/bootstrap/i686-linux/bash)
>
>   I have 1ig8a4bhc7fpw8zrnw4l568wmmcb29rlwg4jbih3imb4x6d9l1gd.
>   If you see something different, your copy is probably corrupt.

The hash is: 1ig8a4bhc7fpw8zrnw4l568wmmcb29rlwg4jbih3imb4x6d9l1gd

> * What does ‘objdump -a gnu/packages/bootstrap/i686-linux/bash’ output?
>   On my x86_64 system, it outputs ‘[...] file format elf32-i386’.

Result is:
--8<---------------cut here---------------start------------->8---
./bash:     file format elf32-i386
--8<---------------cut here---------------end--------------->8---

> * What architecture are you on?

And: x86_64-linux system.

I just updated my system to a8dd285d5a0670abf124a721e6ba94da045b24ba and
am building 76114232d7c140fb9fee84510b72fcfe6ee27714, which failed again.

Early on I installed Guix into a VM, and built the sources in there
on a pretty much default config from the installer.  All tests passed.

Just to be sure I did another clean clone on my main machine, which
failed again.

So why would my system brake the bootstrap binary?  Has it got to do
with a particular package I have in my profile(s)?  I generally build
Guix with ‘guix environment --pure guix.’  I have a second Guix build
machine running.  The packages used there are quite similar, so these
two machines have very similar checkouts and config in general.  Hence,
when I build Guix there, the same error occurs.


Simon




  parent reply	other threads:[~2021-08-28 22:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yguh7fcz5ee.fsf@netpanic.org>
2021-08-26 18:07 ` bug#50212: Tests fail while building Guix Simon Streit
2021-08-27 19:53   ` bug#50212: Several tests fail, Bash fails often. Was: " Simon Streit
2021-08-28 15:00     ` Maxime Devos
2021-08-28 18:13       ` Mark H Weaver
2021-08-28 22:14         ` Simon Streit
2021-08-28 22:32       ` Simon Streit [this message]
2021-08-29 13:06         ` Simon Streit
2021-08-29 21:28           ` Maxim Cournoyer
2021-08-30 18:17             ` Simon Streit
2021-08-30 20:24               ` Maxim Cournoyer
2021-08-28 15:33   ` bug#50212: " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-08-28 21:56     ` Simon Streit

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=yguy28lp5dy.fsf@netpanic.org \
    --to=simon@netpanic.org \
    --cc=50212@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).