From: Roland McGrath <mcgrathr@google.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [COMMITTED PATCH] bfd/doc: Fix racy build failure from missing mkdir
Date: Tue, 25 Jan 2022 14:37:15 -0800 [thread overview]
Message-ID: <CAB=4xhoLpoi6XW=sVUD8YGCmvRewqkYcU62_UYg0YfxOdm76GA@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOoFOfVi9FBN+dnvYNYJmnTe-jRTXLnYwct9QWD4n0=yMw@mail.gmail.com>
Oops! Thanks. I lost track of what all was generated from what.
On Tue, Jan 25, 2022 at 8:56 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Mon, Jan 24, 2022 at 12:45 PM Roland McGrath via Binutils
> <binutils@sourceware.org> wrote:
> >
> > I'm not sure how new this is, but I've started seeing a build failure
> > from bfd/doc not existing in the build directory.
> > Committed as obvious enough.
> >
> > Thanks,
> > Roland
> >
> > bfd/
> > 2022-01-24 Roland McGrath <mcgrathr@google.com>
> >
> > * doc/local.mk (%D%/bfdver.texi): Add mkdir command.
> >
> > diff --git a/bfd/doc/local.mk b/bfd/doc/local.mk
> > index 18a2af1b01d..6a9cceb727a 100644
> > --- a/bfd/doc/local.mk
> > +++ b/bfd/doc/local.mk
> > @@ -127,6 +127,7 @@ REGEN_TEXI = \
> >
> > %D%/bfdver.texi: $(srcdir)/Makefile.in
> > $(AM_V_GEN)\
> > + $(MKDIR_P) $(@D); \
> > echo "@set VERSION $(VERSION)" > $@; \
> > if test -n "$(PKGVERSION)"; then \
> > echo "@set VERSION_PACKAGE $(PKGVERSION)" >> $@; \
>
> I am checking in this.
>
> --
> H.J.
prev parent reply other threads:[~2022-01-25 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 20:44 Roland McGrath
2022-01-25 16:55 ` H.J. Lu
2022-01-25 22:37 ` Roland McGrath [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='CAB=4xhoLpoi6XW=sVUD8YGCmvRewqkYcU62_UYg0YfxOdm76GA@mail.gmail.com' \
--to=mcgrathr@google.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).