public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
	Adam Dinwoodie <adam@dinwoodie.org>
Subject: Re: [PATCH cygport v3] autotools.cygclass: correctly detect Autoconf 2.70+
Date: Wed, 13 Apr 2022 18:58:10 +0100	[thread overview]
Message-ID: <e74165d0-566c-7e89-978e-54f97c8cc30a@dronecode.org.uk> (raw)
In-Reply-To: <20220314221516.13101-1-adam@dinwoodie.org>

On 14/03/2022 22:15, 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.

I applied this.

But it seems no good deed goes unpunished...

>   	configure="${confdir}/configure"
> -	confver=$(grep -m 1 'GNU Autoconf' ${configure} | cut -d ' ' -f 6)
> +	confver="$("$configure" --version | sed -rn 's/.*GNU Autoconf ([0-9\.]+)/\1/p')"
> +	confver_maj=${confver%%.*}
> +	confver_min=${confver##*.}
> +	if [ $confver_maj -ne 2 ]
> +	then
> +		error "unexpected autoconf version";
> +	fi

When rebuilding 'dialog' to update the SRC_URI, I get:

> /usr/share/cygport/cygclass/autotools.cygclass: line 658: [: -ne: unary operator expected
> /usr/share/cygport/cygclass/autotools.cygclass: line 689: [: -ge: unary operator expected
> /usr/share/cygport/cygclass/autotools.cygclass: line 703: [: -ge: unary operator expected

It seems that the configure script for that it customized somehow and 
doesn't output anything matching that regex:

> $ ./configure --version
> 
> Copyright 2003-2020,2021        Thomas E. Dickey
> Copyright 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001
> Free Software Foundation, Inc.
> This configure script is free software; the Free Software Foundation
> gives unlimited permission to copy, distribute and modify it.

I think that if $confver is empty, that should be an error, and then 
perhaps there needs to be a variable which can be set to override 
autodection of the ./configure script version (e.g. something like 
'CONF_VERSION=2.60')


      reply	other threads:[~2022-04-13 17:58 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
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 [this message]

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=e74165d0-566c-7e89-978e-54f97c8cc30a@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).