From: Jon Turney <jon.turney@dronecode.org.uk>
To: Thomas Wolff <towo@towo.net>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: cygport injects unexpected parameter
Date: Wed, 10 May 2023 12:47:33 +0100 [thread overview]
Message-ID: <1ff7292d-237e-4500-b102-1b0e2fa0be56@dronecode.org.uk> (raw)
In-Reply-To: <06d13c30-bde6-12ed-5c8d-4b38d1d40334@towo.net>
On 10/05/2023 08:57, Thomas Wolff via Cygwin-apps wrote:
> I'm trying to build xterm 380 and got two problems in the cygport
> compile step:
>
> 1.
> *** ERROR: could not determine the autoconf version used to generate
> ./configure; perhaps set AUTOCONF_VERSION?
>
> I don't know why a tool wants to be told its own version (or what's
This is not what the error message says.
> going on) but the following line in xterm.cygport seems to help:
> AUTOCONF_VERSION=$( autoconf --version | sed -e "s,.* ,," -e 1q )
Your second point explains the first.
cygport attempts to detect the version of autoconf used to generate the
./configure script, so it knows what options it supports.
If that detection fails (as in this case, because it's generated by
customized version), you can set AUTOCONF_VERSION appropriately.
https://cygwin.github.io/cygport/autotools_cygclass.html#AUTOCONF_VERSION
https://cygwin.com/cgit/cygwin-apps/cygport/tree/cygclass/autotools.cygclass#n711
> 2.
> configure: error: unrecognized option: --docdir=/usr/share/doc/xterm
>
> This seems to be injected by the cygconf function, and the package
> configure script does not know it.
For configure files generated by dickey's variant of autoconf, the
correct thing seems to be to use AUTOCONF_VERSION="2.50"
parent reply other threads:[~2023-05-10 11:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <06d13c30-bde6-12ed-5c8d-4b38d1d40334@towo.net>]
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=1ff7292d-237e-4500-b102-1b0e2fa0be56@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=towo@towo.net \
/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).