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

[Nick Alcock <nick.alcock@oracle.com>]

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)