public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Cc: Richard.Earnshaw@foss.arm.com
Subject: [PATCH/committed] libgloss: enable maintainer mode support
Date: Tue, 22 Feb 2022 17:11:38 -0500	[thread overview]
Message-ID: <20220222221138.29775-1-vapier@gentoo.org> (raw)
In-Reply-To: <6e6ec1c8-70b3-5cc2-3b06-60f516a44ed0@foss.arm.com>

Use AM_MAINTAINER_MODE so devs have to opt-in to automatic rebuilds
of autotools.  This matches what newlib (and most every other GNU
toolchain package) does with automake.
---
 libgloss/Makefile.in  |  9 +++++----
 libgloss/aclocal.m4   | 36 ++++++++++++++++++++++++++++++++++++
 libgloss/configure    | 34 ++++++++++++++++++++++++++++++++++
 libgloss/configure.ac |  1 +
 4 files changed, 76 insertions(+), 4 deletions(-)

diff --git a/libgloss/configure.ac b/libgloss/configure.ac
index b5a0fce08c9b..ec2a49e03704 100644
--- a/libgloss/configure.ac
+++ b/libgloss/configure.ac
@@ -12,6 +12,7 @@ AC_PROG_INSTALL
 
 AC_CANONICAL_SYSTEM
 AM_INIT_AUTOMAKE([foreign no-dist no-define subdir-objects 1.15.1])
+AM_MAINTAINER_MODE
 AM_SILENT_RULES(yes)
 
 if test -z "${with_multisubdir}"; then
-- 
2.34.1


  reply	other threads:[~2022-02-22 22:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 11:57 newlib not building (needs aclocal) Richard Earnshaw
2022-02-22 22:11 ` Mike Frysinger [this message]
2022-02-23 11:26   ` [PATCH/committed] libgloss: enable maintainer mode support Richard Earnshaw
2022-02-23  6:01 ` newlib not building (needs aclocal) Brian Inglis
2022-02-23 11:33   ` Richard Earnshaw
2022-02-24  7:07     ` Mike Frysinger
2022-02-24  7:11       ` Mike Frysinger
2022-02-24  9:08         ` 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=20220222221138.29775-1-vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=Richard.Earnshaw@foss.arm.com \
    --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).