From: Mark Wielaard <mark@klomp.org>
To: binutils@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Tue, 21 Jun 2022 18:40:23 +0200 [thread overview]
Message-ID: <a8d9e59193ab46a916b33ac58da8d9be2dd009f3.camel@klomp.org> (raw)
In-Reply-To: <20220621103204.1C6EB3870847@sourceware.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.
Cheers,
Mark
next prev parent reply other threads:[~2022-06-21 16:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 10:32 builder
2022-06-21 16:40 ` Mark Wielaard [this message]
2022-06-21 17:01 ` Hans-Peter Nilsson
2022-06-21 17:53 ` Nick Alcock
2022-06-21 18:31 ` Nick Alcock
2022-06-21 19:06 ` Hans-Peter Nilsson
2022-06-21 19:32 ` Nick Alcock
-- strict thread matches above, loose matches on Subject: below --
2023-01-09 23:57 ☠ " builder
2023-01-09 23:46 builder
2022-12-16 12:24 builder
2022-12-12 9:54 builder
2022-12-07 4:25 builder
2022-12-05 0:18 builder
2022-11-30 16:24 builder
2022-11-30 16:21 builder
2022-11-11 6:30 builder
2022-11-01 9:58 builder
2022-10-31 13:36 builder
2022-10-19 9:14 builder
2022-07-08 10:24 builder
2022-06-27 11:11 builder
2022-06-13 8:13 builder
2022-06-13 8:18 ` Mark Wielaard
2022-06-13 9:08 ` Jan Beulich
2022-06-09 0:20 builder
[not found] ` <CAG_eJLfRrgsK62e7UX_HF7p5O+czBnTm6z+8K=KnDsasadkp5Q@mail.gmail.com>
2022-06-09 3:36 ` Mark Wielaard
2022-06-02 11:05 builder
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8d9e59193ab46a916b33ac58da8d9be2dd009f3.camel@klomp.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
/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.
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).