From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: autoconf
Date: Thu, 2 Dec 2021 08:19:17 -0500 [thread overview]
Message-ID: <0c9abaef-6147-ffb1-2eb3-245bed608cc1@cornell.edu> (raw)
In-Reply-To: <CAO1jNwsB2Pz39KssoKjBoT3WTNmz35r-TnUkUt0d_=YfZuA9ug@mail.gmail.com>
On 12/2/2021 5:15 AM, Jan Nijtmans via Cygwin-apps wrote:
> Somewhere in cygport, a check is done for the autoconf version, please
> change this check to allow autoconf 2.71 (as well as 2.59 and 2.69).
> Then I can put back the "cygautoreconf" line in tcl.cygport.
You can do this locally until someone gets around to patching cygport. Just
patch /usr/share/cygclass/autotools.cygclass like this:
--- autotools.cygclass~ 2020-05-10 12:06:42.000000000 -0400
+++ autotools.cygclass 2021-12-02 08:14:34.546334100 -0500
@@ -395,7 +395,7 @@
WANT_AUTOCONF=2.5
case $(autoconf --version 2> /dev/null | head -n 1) in
- autoconf*2.[56]?) ;;
+ autoconf*2.[567]?) ;;
*) error "autoconf2.5 is required to build this
package" ;;
esac
Ken
next prev parent reply other threads:[~2021-12-02 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 20:29 autoconf Marco Atzeri
2021-12-01 19:56 ` autoconf Achim Gratz
2021-12-02 6:08 ` autoconf Brian Inglis
2021-12-02 7:23 ` autoconf ASSI
2021-12-02 9:21 ` autoconf Corinna Vinschen
2021-12-02 10:15 ` autoconf Jan Nijtmans
2021-12-02 10:40 ` autoconf Corinna Vinschen
2021-12-02 10:45 ` autoconf Jan Nijtmans
2021-12-02 13:18 ` autoconf ASSI
2021-12-02 13:32 ` autoconf Corinna Vinschen
2021-12-02 16:36 ` autoconf Ken Brown
2021-12-02 13:19 ` Ken Brown [this message]
2021-12-02 18:18 ` autoconf Achim Gratz
2021-12-02 19:41 ` autoconf Achim Gratz
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=0c9abaef-6147-ffb1-2eb3-245bed608cc1@cornell.edu \
--to=kbrown@cornell.edu \
--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).