public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] newlib: require automake-1.11.6
Date: Fri, 31 Dec 2021 17:09:09 +0000 (GMT)	[thread overview]
Message-ID: <20211231170909.0E4393858409@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=1162f09b6cecaa159531e92bf1e26a88eabba771

commit 1162f09b6cecaa159531e92bf1e26a88eabba771
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Thu Dec 30 14:03:30 2021 -0500

    newlib: require automake-1.11.6
    
    This is simply reflecting reality: all the subdirs in here are already
    using automake-1.11.6, so making it a requirement will allow us to stop
    suggesting we might support automake-1.9 or 1.10 (which I'm fairly sure
    do not work today).
    
    This is why only acinclude.m4 changes in this patch: the generated files
    are exactly the same as the directives here are automake constraints,
    not generated code logic.

Diff:
---
 newlib/acinclude.m4 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/newlib/acinclude.m4 b/newlib/acinclude.m4
index 3ec3fe500..3ad0e8906 100644
--- a/newlib/acinclude.m4
+++ b/newlib/acinclude.m4
@@ -120,9 +120,9 @@ AC_SUBST(newlib_basedir)
 
 AC_CANONICAL_HOST
 
-AM_INIT_AUTOMAKE([foreign no-installinfo no-dependencies no-dist no-define 1.9.5])
+AM_INIT_AUTOMAKE([foreign no-installinfo no-dependencies no-dist no-define 1.11.6])
 AM_MAINTAINER_MODE()
-m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES(yes)])
+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


                 reply	other threads:[~2021-12-31 17:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211231170909.0E4393858409@sourceware.org \
    --to=jjohnstn@sourceware.org \
    --cc=newlib-cvs@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).