From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-042.btinternet.com (mailomta20-re.btinternet.com [213.120.69.113]) by sourceware.org (Postfix) with ESMTPS id 949D63858D1E for ; Fri, 30 Sep 2022 13:25:46 +0000 (GMT) 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 Received: from re-prd-rgout-002.btmx-prd.synchronoss.net ([10.2.54.5]) by re-prd-fep-042.btinternet.com with ESMTP id <20220930132545.WINW3291.re-prd-fep-042.btinternet.com@re-prd-rgout-002.btmx-prd.synchronoss.net>; Fri, 30 Sep 2022 14:25:45 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.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@btinternet.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 Received: from [192.168.1.106] (81.153.98.187) by re-prd-rgout-002.btmx-prd.synchronoss.net (5.8.716.04) (authenticated as jonturney@btinternet.com) id 613A8DE83C0AD137; Fri, 30 Sep 2022 14:25:45 +0100 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 Subject: Re: Error when building autoconf2.1, broken package? To: "Carlo B." , The Cygwin Mailing List References: <20220721220657.133463ad30893543b32c38e3@nifty.ne.jp> Content-Language: en-GB In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 List-Id: 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)