public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Naohiro Tamura <naohirot@fujitsu.com>
To: libc-alpha@sourceware.org
Subject: [PATCH 3/3] Removed obsolete AC_CHECK_TOOL_PREFIX
Date: Tue, 16 Feb 2021 12:01:00 +0000	[thread overview]
Message-ID: <20210216120100.213653-1-naohirot@fujitsu.com> (raw)

This patch removed obsolete AC_CHECK_TOOL_PREFIX.
It has been confirmed that AC_CHECK_TOOL_PREFIX is defined as NOP in
GNU 'autoconf' 2.69 [1], so we can safely remove it.
The 'configure' file has been deleted one blank line by the 'autoconf'
2.69 command .

   [1] autoconf-2.69/share/autoconf/autoconf/programs.m4
   181 # AC_CHECK_TOOL_PREFIX
   182 # --------------------
   183 AU_DEFUN([AC_CHECK_TOOL_PREFIX])
---
 configure    | 1 -
 configure.ac | 1 -
 2 files changed, 2 deletions(-)

diff --git a/configure b/configure
index 1dc3af60b4..37cef37413 100755
--- a/configure
+++ b/configure
@@ -4732,7 +4732,6 @@ fi
 fi
 
 # These programs are version sensitive.
-
 for ac_prog in gnumake gmake make
 do
   # Extract the first word of "$ac_prog", so it can be a program name with args.
diff --git a/configure.ac b/configure.ac
index b7f6f8f008..a20c759241 100644
--- a/configure.ac
+++ b/configure.ac
@@ -993,7 +993,6 @@ else
 fi
 
 # These programs are version sensitive.
-AC_CHECK_TOOL_PREFIX
 AC_CHECK_PROG_VER(MAKE, gnumake gmake make, --version,
   [GNU Make[^0-9]*\([0-9][0-9.]*\)],
   [[4-9].* | [1-9][0-9]*], critic_missing="$critic_missing make")
-- 
2.17.1


         reply	other threads:[~2021-02-16 12:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 12:31 [PATCH] Replaced obsoleted AC_HELP_STRING to AS_HELP_STRING Naohiro Tamura
2021-02-15 12:59 ` Adhemerval Zanella
2021-02-15 13:29   ` Mike Frysinger
2021-02-15 13:39     ` Adhemerval Zanella
2021-02-15 15:38       ` Mike Frysinger
2021-02-15 16:39         ` Adhemerval Zanella
2021-02-15 17:17           ` Florian Weimer
2021-02-15 18:51             ` Adhemerval Zanella
2021-02-15 20:21           ` Mike Frysinger
2021-02-15 20:31             ` Adhemerval Zanella
2021-02-16  2:36               ` naohirot
2021-02-16 12:01 ` Naohiro Tamura [this message]
2021-02-16 16:41   ` [PATCH 3/3] Removed obsolete AC_CHECK_TOOL_PREFIX Zack Weinberg
2021-02-17  1:25     ` naohirot
2021-02-21 23:36   ` Mike Frysinger
2021-02-22  1:48     ` naohirot
2021-02-21 21:31 ` [PATCH] Replaced obsoleted AC_HELP_STRING to AS_HELP_STRING Mike Frysinger
2021-02-22  1:41   ` naohirot
2021-02-23  2:02   ` Carlos O'Donell
2021-05-10  0:52     ` naohirot
2021-05-10  1:17       ` Mike Frysinger
2021-05-10  2:15         ` naohirot
2021-05-10 14:16           ` naohirot

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=20210216120100.213653-1-naohirot@fujitsu.com \
    --to=naohirot@fujitsu.com \
    --cc=libc-alpha@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).