public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Adam Dinwoodie <adam@dinwoodie.org>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH cygport] autotools.cygclass: correctly detect Autoconf 2.70+
Date: Sat, 12 Mar 2022 13:02:39 +0000	[thread overview]
Message-ID: <70a9c487-e302-5342-61ce-5b917d089ec6@dronecode.org.uk> (raw)
In-Reply-To: <20220311224005.12377-1-adam@dinwoodie.org>

On 11/03/2022 22:40, Adam Dinwoodie wrote:
> The latest version of Autoconf is 2.71, but the version detection
> incorrectly considers 2.70 and higher as being the same as 2.59 and
> lower for the purposes of specifying documentation directories.  Correct
> that, and make the version detection a bit more future-proof by parsing
> out the actual version parts and performing numeric comparison.
> 
> While we're at it, add a bit more commentary explaining the intent of
> the different behaviour over the different Autoconf versions.
> ---
>   cygclass/autotools.cygclass | 34 +++++++++++++++++++++++-----------
>   1 file changed, 23 insertions(+), 11 deletions(-)
> 
> diff --git a/cygclass/autotools.cygclass b/cygclass/autotools.cygclass
> index cce9be0..2ab5626 100644
> --- a/cygclass/autotools.cygclass
> +++ b/cygclass/autotools.cygclass
> @@ -619,6 +619,8 @@ cygconf() {
>   	local confdir;
>   	local configure;
>   	local confver;
> +	local confver_maj;
> +	local confver_min;
>   	local f;
>   	local foo_config;
>   	local prefix;
> @@ -651,6 +653,8 @@ cygconf() {
>   
>   	configure="${confdir}/configure"
>   	confver=$(grep -m 1 'GNU Autoconf' ${configure} | cut -d ' ' -f 6)
> +	confver_maj=${confver%%.*}
> +	confver_min=${confver##*.}
>   
>   	# AC_CONFIG_FILES should not be dist'ed, but it sometimes happens anyway
>   	eval $(grep -h '^ac_config_files=' ${configure})
> @@ -678,18 +682,26 @@ cygconf() {
>   		confargs+=" --libdir=${prefix}/${MULTILIB_LIBDIR}"
>   	fi
>   
> -	case "x${confver}" in
> -		x2.6[0-9]*)
> -			confargs+=" --docdir=/usr/share/doc/${PN} --htmldir=/usr/share/doc/${PN}/html"
> -			;;
> -		*)
> -			confargs+=" --infodir=${prefix}/share/info --mandir=${prefix}/share/man"
> -			;;
> -	esac
> +	if [ $confver_maj -ge 2 -a $confver_min -ge 60 ] || [ $confver_maj -ge 3 ]

Great. Thanks.

I think it would be acceptable to error on autoconf >=3.0, rather than 
assuming it's going to be autoconf 2.6+ compatible.

  reply	other threads:[~2022-03-12 13:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 16:41 Cygport configure script argument handling Adam Dinwoodie
2022-03-11  5:38 ` Yaakov Selkowitz
2022-03-11  9:05   ` Adam Dinwoodie
2022-03-11 22:40     ` [PATCH cygport] autotools.cygclass: correctly detect Autoconf 2.70+ Adam Dinwoodie
2022-03-12 13:02       ` Jon Turney [this message]
2022-03-13 20:31         ` Adam Dinwoodie
2022-03-13 20:44         ` [PATCH cygport v2] " Adam Dinwoodie
2022-03-14 19:05           ` Jon Turney
2022-03-14 21:05             ` Adam Dinwoodie
2022-03-14 22:15               ` [PATCH cygport v3] " Adam Dinwoodie
2022-04-13 17:58                 ` Jon Turney

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=70a9c487-e302-5342-61ce-5b917d089ec6@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=adam@dinwoodie.org \
    --cc=cygwin-apps@cygwin.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).