☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)

☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)

[builder]

A new failure has been detected on builder binutils-debian-amd64 while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/68/builds/228

Build state: failed compile (failure)
Revision: acd65fa610df09a0954b8fecdadf546215263c5d
Worker: bb1
Build Reason: (unknown)
Blamelist: Nick Clifton <nickc@redhat.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/228/steps/1/logs/stdio

- 2: rm -rf binutils-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/228/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/228/steps/3/logs/stdio

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/228/steps/4/logs/stdio
        - warnings (18): https://builder.sourceware.org/buildbot/#builders/68/builds/228/steps/4/logs/warnings__18_

A new failure has been detected on builder binutils-fedora-x86_64 while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/77/builds/212

Build state: failed compile (failure)
Revision: acd65fa610df09a0954b8fecdadf546215263c5d
Worker: bb2
Build Reason: (unknown)
Blamelist: Nick Clifton <nickc@redhat.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/212/steps/1/logs/stdio

- 2: rm -rf binutils-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/212/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/212/steps/3/logs/stdio

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/212/steps/4/logs/stdio
        - warnings (62): https://builder.sourceware.org/buildbot/#builders/77/builds/212/steps/4/logs/warnings__62_

A new failure has been detected on builder binutils-debian-ppc64 while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/78/builds/212

Build state: failed compile (failure)
Revision: acd65fa610df09a0954b8fecdadf546215263c5d
Worker: debian-ppc64
Build Reason: (unknown)
Blamelist: Nick Clifton <nickc@redhat.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/212/steps/1/logs/stdio

- 2: rm -rf binutils-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/212/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/212/steps/3/logs/stdio

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/212/steps/4/logs/stdio
        - warnings (23): https://builder.sourceware.org/buildbot/#builders/78/builds/212/steps/4/logs/warnings__23_

A new failure has been detected on builder binutils-fedora-ppc64le while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/86/builds/173

Build state: failed compile (failure)
Revision: acd65fa610df09a0954b8fecdadf546215263c5d
Worker: fedora-ppc64le
Build Reason: (unknown)
Blamelist: Nick Clifton <nickc@redhat.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/86/builds/173/steps/1/logs/stdio

- 2: rm -rf binutils-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/86/builds/173/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/86/builds/173/steps/3/logs/stdio

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/86/builds/173/steps/4/logs/stdio
        - warnings (62): https://builder.sourceware.org/buildbot/#builders/86/builds/173/steps/4/logs/warnings__62_

A new failure has been detected on builder binutils-opensuseleap-x86_64 while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/93/builds/92

Build state: failed compile (failure)
Revision: acd65fa610df09a0954b8fecdadf546215263c5d
Worker: bb3
Build Reason: (unknown)
Blamelist: Nick Clifton <nickc@redhat.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/92/steps/1/logs/stdio

- 2: rm -rf binutils-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/92/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/92/steps/3/logs/stdio

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/92/steps/4/logs/stdio
        - warnings (55): https://builder.sourceware.org/buildbot/#builders/93/builds/92/steps/4/logs/warnings__55_

A new failure has been detected on builder binutils-opensusetw-x86_64 while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/102/builds/91

Build state: failed compile (failure)
Revision: acd65fa610df09a0954b8fecdadf546215263c5d
Worker: bb2
Build Reason: (unknown)
Blamelist: Nick Clifton <nickc@redhat.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/102/builds/91/steps/1/logs/stdio

- 2: rm -rf binutils-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/102/builds/91/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/102/builds/91/steps/3/logs/stdio

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/102/builds/91/steps/4/logs/stdio
        - warnings (63): https://builder.sourceware.org/buildbot/#builders/102/builds/91/steps/4/logs/warnings__63_

Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)

[Mark Wielaard]

Hi Nick,

On Tue, 2022-06-21 at 10:32 +0000, builder--- via Binutils wrote:
> A new failure has been detected on builder binutils-debian-amd64
> while building binutils-gdb.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/68/builds/228
> 
> Build state: failed compile (failure)
> Revision: acd65fa610df09a0954b8fecdadf546215263c5d
> Worker: bb1
> Build Reason: (unknown)
> Blamelist: Nick Clifton <nickc@redhat.com>

So that is:

commit acd65fa610df09a0954b8fecdadf546215263c5d (HEAD -> master,
origin/master, origin/HEAD)
Author: Nick Clifton <nickc@redhat.com>
Date:   Tue Jun 21 11:22:38 2022 +0100

    Default to disabling the linker warnings about execstack and RWX
segments if the target is the HPPA architecture.
    
    PR 29263
    * configure.ac (ac_default_ld_warn_execstack): Default to 'no' for
    HPPA targets.
    (ac_default_ld_warn_rwx_segments): Likewise.
    * configure: Regenerate.
    * testsuite/ld-elf/elf.exp: Add the --warn-execstack command line
    option to the command line when running execstack tests for the
    HPPA target.

This failed on all builders:
https://builder.sourceware.org/buildbot/#/changes/2323

And I can reproduce it locally (with a clean build tree):

$ ~/src/binutils-gdb/configure --enable-gold --enable-shared
$ make -j8 all-gas all-ld all-binutils all-gold

make[1]: Entering directory '/opt/local/build/binutils-gdb-obj/ld'
Makefile:2629: .deps/emmo.Pc: No such file or directory
make[1]: *** No rule to make target '.deps/emmo.Pc'.  Stop.

But I have no idea why/how your patch caused it. Maybe because
configure was recreated and sets am__api_version to 1.16 from 1.15?
Wild guess, might be totally unrelated.

Cheers,

Mark

Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)

[Hans-Peter Nilsson]

Hi all.

> From: Mark Wielaard <mark@klomp.org>
>
> Hi Nick,
> 
> On Tue, 2022-06-21 at 10:32 +0000, builder--- via Binutils wrote:
> > A new failure has been detected on builder binutils-debian-amd64
> > while building binutils-gdb.
> > 
> > Full details are available at:
> >     https://builder.sourceware.org/buildbot/#builders/68/builds/228
> > 
> > Build state: failed compile (failure)
> > Revision: acd65fa610df09a0954b8fecdadf546215263c5d
> > Worker: bb1
> > Build Reason: (unknown)
> > Blamelist: Nick Clifton <nickc@redhat.com>
> 
> So that is:
> 
> commit acd65fa610df09a0954b8fecdadf546215263c5d (HEAD -> master,
> origin/master, origin/HEAD)
> Author: Nick Clifton <nickc@redhat.com>
> Date:   Tue Jun 21 11:22:38 2022 +0100
> 
>     Default to disabling the linker warnings about execstack and RWX
> segments if the target is the HPPA architecture.
>     
>     PR 29263
>     * configure.ac (ac_default_ld_warn_execstack): Default to 'no' for
>     HPPA targets.
>     (ac_default_ld_warn_rwx_segments): Likewise.
>     * configure: Regenerate.
>     * testsuite/ld-elf/elf.exp: Add the --warn-execstack command line
>     option to the command line when running execstack tests for the
>     HPPA target.
> 
> This failed on all builders:
> https://builder.sourceware.org/buildbot/#/changes/2323
> 
> And I can reproduce it locally (with a clean build tree):
> 
> $ ~/src/binutils-gdb/configure --enable-gold --enable-shared
> $ make -j8 all-gas all-ld all-binutils all-gold
> 
> make[1]: Entering directory '/opt/local/build/binutils-gdb-obj/ld'
> Makefile:2629: .deps/emmo.Pc: No such file or directory
> make[1]: *** No rule to make target '.deps/emmo.Pc'.  Stop.
> 
> But I have no idea why/how your patch caused it. Maybe because
> configure was recreated and sets am__api_version to 1.16 from 1.15?
> Wild guess, might be totally unrelated.

I had the same confusion when I had a (brief) look into my
own autobuilder failure and made a feeble attempt at
tracking it down.  Maybe a bug in automake-1.16...

Nick: Incidentally, that's not the preferred way to set the
default values; that's in ld/configure.tgt.  As I mentioned
in the bugzilla, see my commit 5d02a15c69c6.  OTOH, if I'm
wrong and miss something, it'd be nice to know, for future
reference.

brgds, H-P

Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)

[Nick Alcock]

On 21 Jun 2022, Hans-Peter Nilsson via Binutils said:

> Hi all.
>
>> commit acd65fa610df09a0954b8fecdadf546215263c5d (HEAD -> master,
>> origin/master, origin/HEAD)
>> Author: Nick Clifton <nickc@redhat.com>
>> Date:   Tue Jun 21 11:22:38 2022 +0100
>> 
>>     Default to disabling the linker warnings about execstack and RWX
>> segments if the target is the HPPA architecture.
>>     
>>     PR 29263
>>     * configure.ac (ac_default_ld_warn_execstack): Default to 'no' for
>>     HPPA targets.
>>     (ac_default_ld_warn_rwx_segments): Likewise.
>>     * configure: Regenerate.
>>     * testsuite/ld-elf/elf.exp: Add the --warn-execstack command line
>>     option to the command line when running execstack tests for the
>>     HPPA target.
[...]
>> make[1]: Entering directory '/opt/local/build/binutils-gdb-obj/ld'
>> Makefile:2629: .deps/emmo.Pc: No such file or directory
>> make[1]: *** No rule to make target '.deps/emmo.Pc'.  Stop.
[...]
> I had the same confusion when I had a (brief) look into my
> own autobuilder failure and made a feeble attempt at
> tracking it down.  Maybe a bug in automake-1.16...

It's pretty clear that this is just another case of regenerating with
the wrong tools. There are changes in the generated configure.ac that I
would not expect from those source changes, and regenerating with
upstream autoconf 2.69 produces a build that works again. So the
ld/configure in that commit was generated with some (distro-patched)
Autoconf by mistake.

-- 
NULL && (void)

Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)

[Nick Alcock]

On 21 Jun 2022, Nick Alcock via Binutils outgrape:

> It's pretty clear that this is just another case of regenerating with
> the wrong tools. There are changes in the generated configure.ac that I
> would not expect from those source changes, and regenerating with
> upstream autoconf 2.69 produces a build that works again. So the
> ld/configure in that commit was generated with some (distro-patched)
> Autoconf by mistake.

Pushed a fix as obvious even though ld/ is not my bailiwick: since I was
literally requalifying my recent patch series for pushing with a quick
bunch of test runs anyway, it was easy to stick this on top :)

(If this caused problems, do let me know, but I kinda doubt it will.)

Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)

[Hans-Peter Nilsson]

> From: Nick Alcock <nick.alcock@oracle.com>
> Date: Tue, 21 Jun 2022 19:53:55 +0200

> >> make[1]: Entering directory '/opt/local/build/binutils-gdb-obj/ld'
> >> Makefile:2629: .deps/emmo.Pc: No such file or directory
> >> make[1]: *** No rule to make target '.deps/emmo.Pc'.  Stop.
> [...]
> > I had the same confusion when I had a (brief) look into my
> > own autobuilder failure and made a feeble attempt at
> > tracking it down.  Maybe a bug in automake-1.16...
> 
> It's pretty clear that this is just another case of regenerating with
> the wrong tools. There are changes in the generated configure.ac that I
> would not expect from those source changes, and regenerating with
> upstream autoconf 2.69 produces a build that works again. So the
> ld/configure in that commit was generated with some (distro-patched)
> Autoconf by mistake.

Well obviously and thanks for fixing it; I don't have my
keys here or I'd done the same.  The behavior was IMHO
interesting nevertheless.  It looks like the .deps directory
wasn't created, whether due to the mixup or an automake
change is still unknown.

The behavior is IMHO unexpected as ./$(DEPDIR)/emmo.Pc is
the *last* included file in ld/Makefile, but a quick
experiment shows that this is indeed a GNU make quirk: the
error message has the last, not the first included file,
that's missing.

brgds, H-P

Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)

[Nick Alcock]

On 21 Jun 2022, Hans-Peter Nilsson via Binutils verbalised:
> Well obviously and thanks for fixing it; I don't have my
> keys here or I'd done the same.  The behavior was IMHO
> interesting nevertheless.  It looks like the .deps directory
> wasn't created, whether due to the mixup or an automake
> change is still unknown.

Yeah. Include handling changed in the misgenerated configure, but the
hunk that broke it was (tabs smushed to spaces, sorry):

-      as_dir=$dirpart/$fdir; as_fn_mkdir_p
-      # echo "creating $dirpart/$file"
-      echo '# dummy' > "$dirpart/$file"
-    done
+    { echo "$as_me:$LINENO: cd "$am_dirpart" \
+      && sed -e '/# am--include-marker/d' "$am_filepart" \
+        | $MAKE -f - am--depfiles" >&5
+   (cd "$am_dirpart" \
+      && sed -e '/# am--include-marker/d' "$am_filepart" \
+        | $MAKE -f - am--depfiles) >&5 2>&5
+   ac_status=$?
+   echo "$as_me:$LINENO: \$? = $ac_status" >&5
+   (exit $ac_status); } || am_rc=$?

The old implementation only needed mkdir: the new one related on make
am--depfiles working, but that's an Automake 1.16 feature, so the make
invocation failed and we never got any $DEPDIRS out of it.

-- 
NULL && (void)