From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Cc: Hans-Peter Nilsson <hp@axis.com>, mark@klomp.org
Subject: Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Tue, 21 Jun 2022 20:32:23 +0100 [thread overview]
Message-ID: <87v8strewo.fsf@esperi.org.uk> (raw)
In-Reply-To: <20220621190607.43E3220417@pchp3.se.axis.com> (Hans-Peter Nilsson via Binutils's message of "Tue, 21 Jun 2022 21:06:07 +0200")
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)
prev parent reply other threads:[~2022-06-21 19:32 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
2022-06-21 19:32 ` Nick Alcock [this message]
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=87v8strewo.fsf@esperi.org.uk \
--to=nick.alcock@oracle.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).