#50031 gcc-core-mesboot1 may not be deterministic

Message #5 received at submit@debbugs.gnu.org (full text, mbox, reply):

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

To: Bug Guix <bug-guix@gnu.org>

Subject: gcc-core-mesboot1 may not be deterministic

Date: Thu, 12 Aug 2021 16:19:37 -0300

Hello,

Using Guix from both the ‘master’ branch¹ and from the ‘core-updates-frozen’
branch², the following command fails:

--8<---------------cut here---------------start------------->8---
$ 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
--8<---------------cut here---------------end--------------->8---

During the stripping phase, there are many of these warnings, which may be
related:

--8<---------------cut here---------------start------------->8---
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'
Usage: strip <option(s)> in-file(s)
 Removes symbols and sections from files
 The options are:
  -I --input-target=<bfdname>      Assume input file is in format <bfdname>
  -O --output-target=<bfdname>     Create an output file in format <bfdname>
  -F --target=<bfdname>            Set both input and output format to <bfdname>
  -p --preserve-dates              Copy modified/access timestamps to the output
  -R --remove-section=<name>       Remove section <name> from the output
  -s --strip-all                   Remove all symbol and relocation information
  -g -S -d --strip-debug           Remove all debugging symbols
     --strip-unneeded              Remove all symbols not needed by relocations
  -N --strip-symbol=<name>         Do not copy symbol <name>
  -K --keep-symbol=<name>          Only copy symbol <name>
  -x --discard-all                 Remove all non-global symbols
  -X --discard-locals              Remove any compiler-generated symbols
  -v --verbose                     List all object files modified
  -V --version                     Display this program's version number
  -h --help                        Display this output
     --info                        List object formats & architectures supported
  -o <file>                        Place stripped output into <file>
strip: supported targets: elf32-i386 a.out-i386-linux efi-app-ia32 elf32-little elf32-big srec symbolsrec tekhex binary ihex trad-core
--8<---------------cut here---------------end--------------->8---

-- 
Thanks,
Thiago


¹ commit eb0abba3877c0caeac24d0f9c71f31420dba8d6b
² commit a3fc64e4f159b601c18d091713f9c76c01b010aa

Message #12 received at 50031@debbugs.gnu.org (full text, mbox, reply):

From: Ludovic Courtès <ludo@gnu.org>

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

Cc: 50031@debbugs.gnu.org

Subject: Re: bug#50031: gcc-core-mesboot1 may not be deterministic

Date: Mon, 20 Sep 2021 09:11:13 +0200

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’.

Message #15 received at 50031@debbugs.gnu.org (full text, mbox, reply):

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

To: Ludovic Courtès <ludo@gnu.org>

Cc: 50031@debbugs.gnu.org

Subject: Re: bug#50031: gcc-core-mesboot1 may not be deterministic

Date: Mon, 20 Sep 2021 22:33:09 -0300

Hello Ludo,

Em segunda-feira, 20 de setembro de 2021, às 04:11:13 -03, Ludovic Courtès 
escreveu:
> 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.d
> > rv' may not be deterministic: output
> > `/gnu/store/rn3qvn67nraicabvlrx1rhw6nsjrpgpx-gcc-core-mesboot1-4.6.4'
> > differs
> 
> 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.

Thank you for mentioning that discussion. I should have found that before 
filing this issue. Sorry for the duplicate  report.

-- 
Thanks,
Thiago

Send a report that this bug log contains spam.