X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 949D63858D1E
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=dronecode.org.uk
Authentication-Results:	sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk
Authentication-Results:	btinternet.com;
	auth=pass (PLAIN) smtp.auth=jonturney AT btinternet DOT com;
	bimi=skipped
X-SNCR-Rigid:	613A8DE83C0AD137
X-Originating-IP:	[81.153.98.187]
X-OWM-Source-IP:	81.153.98.187 (GB)
X-OWM-Env-Sender:	jonturney AT btinternet DOT com
X-VadeSecure-score:	verdict=clean score=0/300, class=clean
X-RazorGate-Vade:	gggruggvucftvghtrhhoucdtuddrgedvfedrfeehvddgieefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfhuffvfhgjtgfgsehtjeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpeegteejueevgeehffdukeegffduhffhteffheehjedvfeefgfekffelgfdtteelgeenucfkphepkedurdduheefrdelkedrudekjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddtiegnpdhinhgvthepkedurdduheefrdelkedrudekjedpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhnsggprhgtphhtthhopedvpdhrtghpthhtoheptggrrhhlohdrsghrrghmihhnihesghhmrghilhdrtghomhdprhgtphhtthhopegthihgfihinhestgihghifihhnrdgtohhm
X-RazorGate-Vade-Verdict:	clean 0
X-RazorGate-Vade-Classification:	clean
Message-ID:	<135d5f0a-1141-8b16-793c-d41535f4eae9@dronecode.org.uk>
Date:	Fri, 30 Sep 2022 14:25:45 +0100
MIME-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
	Thunderbird/102.3.0
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Subject:	Re: Error when building autoconf2.1, broken package?
To:	"Carlo B." <carlo DOT bramini AT gmail DOT com>,
	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<CADt9576yap6_9=wcZDLKsUqz4bAaP3yOexVs_wykJFfGg3W+=Q AT mail DOT gmail DOT com>
	<20220721220657 DOT 133463ad30893543b32c38e3 AT nifty DOT ne DOT jp>
	<CADt9574Yo=BRc26A4FdGucoEOjXV+kRsJ3BrDCzLSaejU_r+pQ AT mail DOT gmail DOT com>
	<de8f1bd6-8d7f-792a-6074-abfa3e655c8d AT dronecode DOT org DOT uk>
	<CADt957675oM9Ro=19yd2OSeuo41X2Xp7i6xpSsZbvJchj9PnJA AT mail DOT gmail DOT com>
In-Reply-To:	<CADt957675oM9Ro=19yd2OSeuo41X2Xp7i6xpSsZbvJchj9PnJA@mail.gmail.com>
X-Spam-Status:	No, score=-3569.1 required=5.0 tests=BAYES_00, FORGED_SPF_HELO,
	KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A,
	RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_NONE,
	TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On 10/08/2022 11:35, Carlo B. wrote:
> Il giorno mer 3 ago 2022 alle ore 21:52 Jon Turney
> <jon DOT turney AT dronecode DOT org DOT uk> 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)


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -