From: "H.J. Lu" <hjl.tools@gmail.com>
To: Binutils <binutils@sourceware.org>
Cc: Tobias Burnus <tobias@codesourcery.com>, Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] bfd: Make bfd.stamp depend on source bfd.texi
Date: Wed, 26 Jan 2022 05:29:03 -0800 [thread overview]
Message-ID: <CAMe9rOq81evuuGmBo-WyT3Knzmn_HkaT-W2hvx=zrJWw6LkeYw@mail.gmail.com> (raw)
In-Reply-To: <20220125171527.209521-1-hjl.tools@gmail.com>
On Tue, Jan 25, 2022 at 9:15 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> Make bfd.stamp depend on source bfd.texi to avoid regenerating
> doc/bfd.info for each make run.
>
> PR binutils/28807
> * Makefile.in: Regenerate.
> * doc/local.mk (%D%/bfd.stamp): Depend on $(srcdir)/%D%/bfd.texi.
> ---
> bfd/Makefile.in | 5 +++--
> bfd/doc/local.mk | 5 +++--
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/bfd/Makefile.in b/bfd/Makefile.in
> index 5a9b32cd25c..b8e5ea0153f 100644
> --- a/bfd/Makefile.in
> +++ b/bfd/Makefile.in
> @@ -2504,8 +2504,9 @@ doc/%.stamp: $(srcdir)/%.h $(srcdir)/doc/doc.str $(MKDOC) doc/$(am__dirstamp)
> doc/%.stamp: $(srcdir)/%.c $(srcdir)/doc/doc.str $(MKDOC) doc/$(am__dirstamp)
> $(AM_V_GEN)$(REGEN_TEXI)
>
> -# Avoid the %.stamp generating a builddir/bfd.texi that overrides the srcdir/.
> -doc/bfd.stamp: doc/$(am__dirstamp) ; $(AM_V_at)touch $@
> +# Avoid the %.stamp generating a builddir/bfd.texi that overrides the
> +# srcdir/ as well as regenerating doc/bfd.info for each make run.
> +doc/bfd.stamp: $(srcdir)/doc/bfd.texi ; $(AM_V_at)touch $@
>
> # We use bfdt.texi, rather than bfd.texi, to avoid conflicting with
> # bfd.texi on an 8.3 filesystem.
> diff --git a/bfd/doc/local.mk b/bfd/doc/local.mk
> index 9bf4815d8c6..931942f874c 100644
> --- a/bfd/doc/local.mk
> +++ b/bfd/doc/local.mk
> @@ -118,8 +118,9 @@ REGEN_TEXI = \
> %D%/%.stamp: $(srcdir)/%.c $(srcdir)/%D%/doc.str $(MKDOC) %D%/$(am__dirstamp)
> $(AM_V_GEN)$(REGEN_TEXI)
>
> -# Avoid the %.stamp generating a builddir/bfd.texi that overrides the srcdir/.
> -%D%/bfd.stamp: %D%/$(am__dirstamp) ; $(AM_V_at)touch $@
> +# Avoid the %.stamp generating a builddir/bfd.texi that overrides the
> +# srcdir/ as well as regenerating doc/bfd.info for each make run.
> +%D%/bfd.stamp: $(srcdir)/%D%/bfd.texi ; $(AM_V_at)touch $@
>
> # We use bfdt.texi, rather than bfd.texi, to avoid conflicting with
> # bfd.texi on an 8.3 filesystem.
> --
> 2.34.1
>
I am checking it in.
--
H.J.
prev parent reply other threads:[~2022-01-26 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 17:15 H.J. Lu
2022-01-26 13:29 ` H.J. Lu [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='CAMe9rOq81evuuGmBo-WyT3Knzmn_HkaT-W2hvx=zrJWw6LkeYw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=tobias@codesourcery.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).