From: Jon Turney <jon.turney@dronecode.org.uk>
To: Mike Frysinger <vapier@gentoo.org>,
"newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: [PATCH 4/5 v3] newlib: move man page generation into top-level build
Date: Tue, 1 Feb 2022 14:37:48 +0000 [thread overview]
Message-ID: <40acd8d2-b43f-e65e-d612-93d327a3052e@dronecode.org.uk> (raw)
In-Reply-To: <20220201062107.19266-4-vapier@gentoo.org>
On 01/02/2022 06:21, Mike Frysinger wrote:
> +%D%/libc.xml.stamp: %D%/libc.in.xml $(LIBC_CHAPTERS) $(LIBC_DOCBOOK_OUT_FILES)
> + $(AM_V_at)\
> + for chapter in $(LIBC_CHAPTERS); do \
> + $(TEXI2DOCBOOK) < $(srcdir)/$$chapter > %D%/`basename $${chapter%.tex}`.xml || exit 1; \
> + done
> + $(AM_V_GEN)xsltproc --xinclude --path $(builddir)/%D% --nonet $(srcdir)/refcontainers.xslt $< > $@.tmp
> + $(AM_V_at)$(SHELL) $(newlib_basedir)/../move-if-change $@.tmp $(@:.stamp=)
> + $(AM_V_at)touch $@
> +%D%/libc.xml: %D%/libc.xml.stamp; @true
This doesn't seem right.
This rule produces a single output with a definite name 'lib.xml', so
there's no need for a timestamp file?
next prev parent reply other threads:[~2022-02-01 14:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 4:32 [PATCH 0/5] migrate documentation into top-level Mike Frysinger
2022-01-22 4:32 ` [PATCH 1/5] newlib: libm: move manual into top-level build Mike Frysinger
2022-01-22 4:32 ` [PATCH 2/5] newlib: libc: include all chapters all the time in the manual Mike Frysinger
2022-01-22 4:32 ` [PATCH 3/5] newlib: libc: move manual into top-level build Mike Frysinger
2022-01-24 14:30 ` Corinna Vinschen
2022-01-22 4:32 ` [PATCH 4/5] newlib: move man page generation " Mike Frysinger
2022-01-22 4:32 ` [PATCH 5/5] newlib: drop shared documentation rules Mike Frysinger
2022-01-28 7:58 ` [PATCH 1/5 v2] newlib: libm: move manual into top-level build Mike Frysinger
2022-01-28 7:58 ` [PATCH 2/5 v2] newlib: libc: include all chapters all the time in the manual Mike Frysinger
2022-01-28 7:58 ` [PATCH 3/5 v2] newlib: libc: move manual into top-level build Mike Frysinger
2022-01-28 7:58 ` [PATCH 4/5 v2] newlib: move man page generation " Mike Frysinger
2022-01-28 7:58 ` [PATCH 5/5 v2] newlib: drop shared documentation rules Mike Frysinger
2022-01-31 14:58 ` [PATCH 1/5 v2] newlib: libm: move manual into top-level build Jon Turney
2022-02-01 3:40 ` Mike Frysinger
2022-02-01 14:37 ` Jon Turney
2022-02-01 6:21 ` [PATCH 1/5 v3] " Mike Frysinger
2022-02-01 6:21 ` [PATCH 2/5 v3] newlib: libc: include all chapters all the time in the manual Mike Frysinger
2022-02-01 6:21 ` [PATCH 3/5 v3] newlib: libc: move manual into top-level build Mike Frysinger
2022-02-01 6:21 ` [PATCH 4/5 v3] newlib: move man page generation " Mike Frysinger
2022-02-01 14:37 ` Jon Turney [this message]
2022-02-01 23:12 ` Mike Frysinger
2022-02-01 6:21 ` [PATCH 5/5 v3] newlib: drop shared documentation rules Mike Frysinger
2022-02-05 12:13 ` [PATCH 1/5 v3] newlib: libm: move manual into top-level build Corinna Vinschen
2022-02-05 18:04 ` Mike Frysinger
2022-02-07 10:30 ` Corinna Vinschen
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=40acd8d2-b43f-e65e-d612-93d327a3052e@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).