From: Jon Turney <jon.turney@dronecode.org.uk>
To: newlib@sourceware.org
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH] Enable automake silent rules
Date: Tue, 7 Dec 2021 12:56:24 +0000 [thread overview]
Message-ID: <20211207125624.5465-1-jon.turney@dronecode.org.uk> (raw)
Use AM_SILENT_RULES, to enable automake silent rules (by default), if we
are using a version of automake which supports it (>=1.11).
Silent rules can be disabled by configuring with '--disable-silent-rules',
or invoking 'make V=1'.
For ease of reviewing, this patch doesn't contain configure and
Makefile.in regeneration.
Future work: There are a few compilations which are not silenced by
this, as they use custom rules.
---
newlib/acinclude.m4 | 1 +
1 file changed, 1 insertion(+)
diff --git a/newlib/acinclude.m4 b/newlib/acinclude.m4
index 05e545c9f..42af6b548 100644
--- a/newlib/acinclude.m4
+++ b/newlib/acinclude.m4
@@ -121,6 +121,7 @@ AC_SUBST(newlib_basedir)
AC_CANONICAL_HOST
AM_INIT_AUTOMAKE([cygnus no-define 1.9.5])
+m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES(yes)])
# FIXME: We temporarily define our own version of AC_PROG_CC. This is
# copied from autoconf 2.12, but does not call AC_PROG_CC_WORKS. We
--
2.34.1
next reply other threads:[~2021-12-07 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 12:56 Jon Turney [this message]
2021-12-07 14:16 ` Corinna Vinschen
[not found] ` <DM3P110MB05226CEB561AD8A4639848CD9A6E9@DM3P110MB0522.NAMP110.PROD.OUTLOOK.COM>
2021-12-07 16:10 ` Fw: " C Howland
2021-12-07 19:52 ` Mike Frysinger
2021-12-07 20:03 ` C Howland
2021-12-08 6:26 ` Brian Inglis
2021-12-07 20:12 ` Jon Turney
2021-12-08 9:49 ` Corinna Vinschen
[not found] ` <DM3P110MB05226D9DD3776B639F45F2599A6F9@DM3P110MB0522.NAMP110.PROD.OUTLOOK.COM>
2021-12-08 15:41 ` Fw: " C Howland
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=20211207125624.5465-1-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=newlib@sourceware.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).