unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: 50031@debbugs.gnu.org
Subject: bug#50031: gcc-core-mesboot1 may not be deterministic
Date: Mon, 20 Sep 2021 09:11:13 +0200	[thread overview]
Message-ID: <87k0jbrab2.fsf@gnu.org> (raw)
In-Reply-To: <3505331.lUEJ2uQ5fA@popigai> (Thiago Jung Bauermann's message of "Thu, 12 Aug 2021 16:19:37 -0300")

Hi Thiago,

Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:

> Using Guix from both the ‘master’ branch¹ and from the ‘core-updates-frozen’
> branch², the following command fails:
>
> $ guix build --check \
>     -e '(@@ (gnu packages commencement) gcc-core-mesboot1)’
>     ⋮
> guix build: erro: derivation `/gnu/store/qbnxfv7v7288iisl44kccz68k0pv9qdi-gcc-core-mesboot1-4.6.4.drv' may not be deterministic: output `/gnu/store/rn3qvn67nraicabvlrx1rhw6nsjrpgpx-gcc-core-mesboot1-4.6.4' differs
>
>
> During the stripping phase, there are many of these warnings, which may be
> related:
>
> starting phase `strip'
> stripping binaries in "/gnu/store/rn3qvn67nraicabvlrx1rhw6nsjrpgpx-gcc-core-mesboot1-4.6.4/lib" with "strip" and flags ("--strip-debug" "--enable-deterministic-archives")
> strip: unrecognized option `--enable-deterministic-archives'

This was discussed in <https://issues.guix.gnu.org/45962>.  There’s the
beginning of a patch there that needs to be adapted to avoid depending
on xz at this early stage, I think.

Thanks,
Ludo’.




  reply	other threads:[~2021-09-20  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 19:19 bug#50031: gcc-core-mesboot1 may not be deterministic Thiago Jung Bauermann via Bug reports for GNU Guix
2021-09-20  7:11 ` Ludovic Courtès [this message]
2021-09-21  1:33   ` Thiago Jung Bauermann via Bug reports for GNU Guix

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=87k0jbrab2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=50031@debbugs.gnu.org \
    --cc=bauermann@kolabnow.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 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).