From: Hans-Peter Nilsson <hp@axis.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: <binutils@sourceware.org>, <mark@klomp.org>, <nickc@redhat.com>
Subject: Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Tue, 21 Jun 2022 21:06:07 +0200 [thread overview]
Message-ID: <20220621190607.43E3220417@pchp3.se.axis.com> (raw)
In-Reply-To: <874k0dsy18.fsf@esperi.org.uk> (message from Nick Alcock on Tue, 21 Jun 2022 19:53:55 +0200)
> 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
next prev parent reply other threads:[~2022-06-21 19:06 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
2022-06-21 19:06 ` Hans-Peter Nilsson [this message]
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=20220621190607.43E3220417@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=binutils@sourceware.org \
--cc=mark@klomp.org \
--cc=nick.alcock@oracle.com \
--cc=nickc@redhat.com \
/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).