public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: cygport injects unexpected parameter
Date: Wed, 10 May 2023 10:22:02 -0600	[thread overview]
Message-ID: <94b454a2-57e2-56e8-4c69-6c2505de98d1@Shaw.ca> (raw)
In-Reply-To: <06d13c30-bde6-12ed-5c8d-4b38d1d40334@towo.net>

On 2023-05-10 01: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 going on) 
> but the following line in xterm.cygport seems to help:
> AUTOCONF_VERSION=$( autoconf --version | sed -e "s,.* ,," -e 1q )

As part of autoreconf, it tries to figure out what version of autoconf should be 
used for configure.
Thomas Dickey uses his own autoconf package without a version definition.
For his Cygwin packages AUTOCONF_VERSION=2.52 tells autoconf to behave like his.

> 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.

You could skip cygconf and run autoreconf ... then $S/configure with the other 
--...dir and option variables required.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

      reply	other threads:[~2023-05-10 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10  7:57 Thomas Wolff
2023-05-10 16:22 ` Brian Inglis [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=94b454a2-57e2-56e8-4c69-6c2505de98d1@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --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).