public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Naohiro Tamura <naohirot@fujitsu.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Replaced obsoleted AC_HELP_STRING to AS_HELP_STRING
Date: Mon, 15 Feb 2021 10:38:52 -0500	[thread overview]
Message-ID: <YCqVjG7DXqQk5yYP@vapier> (raw)
In-Reply-To: <060cf851-b2c9-a608-7dbb-7f7a4636ea6a@linaro.org>

On 15 Feb 2021 10:39, Adhemerval Zanella wrote:
> On 15/02/2021 10:29, Mike Frysinger wrote:
> > On 15 Feb 2021 09:59, Adhemerval Zanella via Libc-alpha wrote:
> >> On 15/02/2021 09:31, Naohiro Tamura wrote:
> >>> This patch replaced obsoleted AC_HELP_STRING to AS_HELP_STRING.
> >>> As of Glibc 2.33, INSTALL says "GNU 'autoconf' 2.69 (exactly)" is
> >>> required. So we can safely replace obsoleted macro without worrying
> >>> about older autoconf.
> >>> This change doesn't affect the contents of "configure" file.
> >>
> >> If this does not change or improve configure, why change configure.ac
> >> then?
> > 
> > why wait for autoconf to start warning that we're using a deprecated
> > macro and failing the build or confusing devs ?
> > 
> > patch LGTM
> 
> Because we use a macro to test for the specific autoconf version:

that's not an argument for continuing to use deprecated macros

> aclocal.m4:
> 
>   5 m4_define([GLIBC_AUTOCONF_VERSION], [2.69])
>   6 m4_if(m4_defn([AC_AUTOCONF_VERSION]), GLIBC_AUTOCONF_VERSION, [],
>   7       [m4_fatal(m4_flatten(
>   8 Exactly version GLIBC_AUTOCONF_VERSION of Autoconf is required but you have
>   9 m4_defn([AC_AUTOCONF_VERSION])
> 
> So autoconf will start to fail or dumping a warning only if the
> distro actually patch it to do so.
> 
> I don't have a strong opinion about this patch, but due the *current*
> constraints of the auto-generation (which requires an specific autoconf
> version), this patch does not improve anything really.

the macro is clearly deprecated upstream.  the version we're pinned to supports
the non-deprecated version.  i don't see why we're debating this.

it's a lot easier to upgrade versions when you don't have to dig through a pile
of warnings in the process.  if people want to do migrations ahead of time (and
have even written the patches), then let's merge them.
-mike

  reply	other threads:[~2021-02-15 15:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 12:31 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 [this message]
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 ` [PATCH 3/3] Removed obsolete AC_CHECK_TOOL_PREFIX Naohiro Tamura
2021-02-16 16:41   ` 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=YCqVjG7DXqQk5yYP@vapier \
    --to=vapier@gentoo.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=naohirot@fujitsu.com \
    /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).