From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: Mike Frysinger <vapier@gentoo.org>,
Zack Weinberg <zackw@panix.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] configure.ac: Update AC_PROG_AR related comment
Date: Tue, 10 Jan 2023 17:14:14 +0100 [thread overview]
Message-ID: <Y72O1pYaHt6u1FvN@pevik> (raw)
In-Reply-To: <87lemaivkv.fsf@suse.de>
Hi Richie,
thanks for your review.
> > AC_PROG_CC
> > -# <= autoconf 2.61 doesn't have AC_PROG_AR, but 2.63 has it. Not sure about
> > -# 2.62.
> > +# autoconf >= v2.72a
> This reads like we need the def for autoconf => v2.72a. How about
You're right. I probably thought this is defined since v2.72a,
thus not needed.
> # for autoconfig < v2.72a
This is much better, I'll merge it as this (unless anybody objects).
> Also which distro(s) do we support which have < v2.72a? We maybe can
> include that here *if known*.
I'm not sure if v2.72a (alpha?) is shipped to any distro. v2.72 haven't been
released yet.
The reason to update the comment was
1) don't confuse with very old version (it's still needed)
2) notify users once v2.72 is released and shipped in case of problems.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-01-10 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:45 [LTP] [PATCH 1/2] configure.ac: Require 2.64 Petr Vorel
2023-01-03 12:45 ` [LTP] [PATCH 2/2] configure.ac: Update AC_PROG_AR related comment Petr Vorel
2023-01-10 9:25 ` Richard Palethorpe
2023-01-10 16:14 ` Petr Vorel [this message]
2023-01-10 19:03 ` Zack Weinberg
2023-01-10 20:12 ` Petr Vorel
2023-01-12 10:21 ` Richard Palethorpe
2023-01-03 13:30 ` [LTP] [PATCH 1/2] configure.ac: Require 2.64 Petr Vorel
2023-01-04 3:07 ` Li Wang
2023-01-04 9:11 ` Petr Vorel
2023-01-04 9:37 ` Li Wang
2023-01-10 9:48 ` Richard Palethorpe
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=Y72O1pYaHt6u1FvN@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
--cc=vapier@gentoo.org \
--cc=zackw@panix.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