From: Jon Turney <jon.turney@dronecode.org.uk>
To: Mike Frysinger <vapier@gentoo.org>,
"newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: [PATCH 1/5 v2] newlib: libm: move manual into top-level build
Date: Mon, 31 Jan 2022 14:58:54 +0000 [thread overview]
Message-ID: <bfe04a31-fee4-3da6-cd54-54c1d4d68674@dronecode.org.uk> (raw)
In-Reply-To: <20220128075826.1813-1-vapier@gentoo.org>
On 28/01/2022 07:58, Mike Frysinger wrote:
> This doesn't migrate all the docs, just the libm's manual (pdf/info).
> This is to show the basic form of migrating the chew files.
[...]
> diff --git a/newlib/libm/Makefile.inc b/newlib/libm/Makefile.inc
> new file mode 100644
> index 000000000000..9aa5a5c93519
> --- /dev/null
> +++ b/newlib/libm/Makefile.inc
> @@ -0,0 +1,26 @@
> +info_TEXINFOS += %D%/libm.texi
> +%C%_libm_TEXINFOS = %D%/targetdep.tex $(LIBM_CHEWOUT_FILES)
> +
> +LIBM_CHEWOUT_FILES =
> +
> +LIBM_CHAPTERS =
> +
> +%D%/libm.dvi: %D%/targetdep.tex $(LIBM_CHEWOUT_FILES)
> +
> +%D%/targetdep.tex: $(LIBM_CHAPTERS)
> + $(AM_V_GEN)cat $^ > $@.tmp
> + $(AM_V_at)$(SHELL) $(newlib_basedir)/../move-if-change $@.tmp $@
> + $(AM_V_at)touch $@
We carefully only update $@ if it's changed, then touch it anyhow?
This seems like a transcription error, since originally we were touching
a timestamp file, or perhaps leftover from testing?
The same pattern occurs later, as well.
> --- a/newlib/libm/common/Makefile.am
> +++ b/newlib/libm/common/Makefile.am
> @@ -59,15 +59,11 @@ endif # USE_LIBTOOL
>
> include $(srcdir)/../../Makefile.shared
>
> -CHEWOUT_FILES = s_cbrt.def s_copysign.def s_exp10.def s_expm1.def s_ilogb.def \
> - s_infinity.def s_isnan.def s_log1p.def s_modf.def \
> - s_nan.def s_nextafter.def s_pow10.def s_scalbn.def \
> - s_fdim.def s_fma.def s_fmax.def s_fmin.def \
> - s_logb.def s_log2.def s_lrint.def s_lround.def s_nearbyint.def \
> - s_remquo.def s_rint.def s_round.def s_signbit.def s_trunc.def \
> - isgreater.def
> -
> -CHAPTERS =
> +LIBM_CHEWOUT_FILES =
> +LIBM_CHAPTERS =
> +include ./Makefile.inc
Is this boilerplate really needed before including the makefile
fragment, since '+=' should work even if the variable isn't already defined?
> +CHEWOUT_FILES = $(LIBM_CHEWOUT_FILES)
> +CHAPTERS = $(LIBM_CHAPTERS)
>
> # A partial dependency list.
>
next prev parent reply other threads:[~2022-01-31 14:59 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 ` Jon Turney [this message]
2022-02-01 3:40 ` [PATCH 1/5 v2] newlib: libm: move manual into top-level build 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
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=bfe04a31-fee4-3da6-cd54-54c1d4d68674@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).