From: Nick Alcock <nick.alcock@oracle.com>
To: binutils <binutils@sourceware.org>
Cc: Nick Alcock <nick.alcock@oracle.com>,
Hans-Peter Nilsson <hp@axis.com>, Mark Wielaard <mark@klomp.org>,
Alan Modra <amodra@gmail.com>
Subject: Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Tue, 21 Jun 2022 19:31:33 +0100 [thread overview]
Message-ID: <87zgi5rhq2.fsf@esperi.org.uk> (raw)
In-Reply-To: <874k0dsy18.fsf@esperi.org.uk> (Nick Alcock via Binutils's message of "Tue, 21 Jun 2022 18:53:55 +0100")
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.)
next prev parent reply other threads:[~2022-06-21 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 10:32 ☠ " builder
2022-06-21 16:40 ` Mark Wielaard
2022-06-21 17:01 ` Hans-Peter Nilsson
2022-06-21 17:53 ` Nick Alcock
2022-06-21 18:31 ` Nick Alcock [this message]
2022-06-21 19:06 ` Hans-Peter Nilsson
2022-06-21 19:32 ` Nick Alcock
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=87zgi5rhq2.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hp@axis.com \
--cc=mark@klomp.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).