public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
To: "Carlo B." <>,
	The Cygwin Mailing List <>
Subject: Re: Error when building autoconf2.1, broken package?
Date: Fri, 30 Sep 2022 14:25:45 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 10/08/2022 11:35, Carlo B. wrote:
> Il giorno mer 3 ago 2022 alle ore 21:52 Jon Turney
> <> ha scritto:
>> On 22/07/2022 15:44, Carlo B. wrote:
>>> it works, thank you very much.
>>> I also added AUTOCONF_VERSION=2.13 directly into the cygport script,
>>> before calling cygconf and it also worked fine without manually
>>> setting that environment variable.
>>> I think that it would be worth to update the cygport script into
>>> autoconf2.1-2.13-12-src.tar.bz2 to make it working again also for
>>> other people.
>> Is there something wrong with our supplied autconf2.1 package?
> Nowadays, it is not possible to make the autconf2.1 package from "src"
> because the errors written in previous emails.
> I don't know if the fault is caused by a regression into cygport or it
> is needed to fix the "src" package of autconf2.1 for supporting a new
> syntax or something like that. Unfortunately, the main problem is that
> running the cygport script for autoconf 2.1 still hangs, so perhaps it
> would be useful to fix it, in one way or another one.
> Thank you very much for your time and your reply.

This isn't really responsive to my question: Are you building an 
autoconf2.1 package because the one we provide is deficient in some way, 
or because you want to?

>> This is a regression in cygport, which I'll see about fixing.

This should be fixed as of cygport 0.35.3

>> (Briefly: cygport tries to detect the version of autoconf which was used
>> to generate the ./configure script, so it knows what option arguments to
>> supply to it.  Recently this was extended to detect autoconf 2.7x, but
>> that seems to have broken detecting autoconf 2.1x)

      reply	other threads:[~2022-09-30 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 10:42 Carlo B.
2022-07-21 13:06 ` Takashi Yano
2022-07-22 14:44   ` Carlo B.
2022-08-03 19:52     ` Jon Turney
2022-08-10 10:35       ` Carlo B.
2022-09-30 13:25         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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