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 40EDF3858D39
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=SystematicSw.ab.ca
Authentication-Results:	sourceware.org;
	spf=none smtp.mailfrom=systematicsw.ab.ca
X-Authority-Analysis:	v=2.4 cv=P+4pOwMu c=1 sm=1 tr=0 ts=619188b1
	a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17
	a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=NEAV23lmAAAA:8 a=uYT-Tk0qkVT609LjNaIA:9
	a=QEXdDO2ut3YA:10 a=sRI3_1zDfAgwuvI8zelB:22
Message-ID:	<ac00dcf4-dc8b-5522-06ad-19ca3b1ae00e@SystematicSw.ab.ca>
Date:	Sun, 14 Nov 2021 15:07:45 -0700
MIME-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
	Thunderbird/91.3.0
Subject:	Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
To:	cygwin AT cygwin DOT com
References:	<9b0f1bad-1fde-1ed0-a454-409be5c97c10 AT SystematicSw DOT ab DOT ca>
	<87o86m9a2w DOT fsf AT Rainer DOT invalid>
	<47af4ee4-c63a-13b3-b6fa-2ee792b84120 AT SystematicSw DOT ab DOT ca>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Organization:	Systematic Software
In-Reply-To:	<47af4ee4-c63a-13b3-b6fa-2ee792b84120@SystematicSw.ab.ca>
X-CMAE-Envelope:	MS4xfGTe6ZMnsRqNE2dIytgTpwCYuogfnlbVARXTc7Ar9J9Ao5BsWbnrbJHAKYtJUvwDP3QG3q2yKDf1ezWQlth8l36kRRZYQcroD1IbRLySVNupfbuODI4l
	TVP1AaODsFD7oRUCJDmWItYL399MFlQh05YZDF8AonhRak6qPTcTVsGyFGXZRh5XoK6+/iX/g4tvJVwH/UePuKjyNMYbg+Cuqqk=
X-Spam-Status:	No, score=-1165.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL,
	RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,
	SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) 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>
Reply-To:	cygwin AT cygwin DOT com
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 2021-11-14 06:49, Brian Inglis wrote:
> On 2021-11-14 05:48, Achim Gratz wrote:
>> Brian Inglis writes:
>>> Got these errors trying to build latest ncurses on my system, so
>>> retried on scallywag and got same result, with no clue where that is
>>> coming from!
> 
>> Unless there is absolutely no other way and you know exactly what you're
>> doing, never skip the cygautoreconf in src_compile.
> 
> I always try to use the default src_compile autotools.cygclass function 
> where possible to ensure that is the case.
> Various GNU tool builds have that commented out by their previous 
> experienced maintainers, so I tread carefully.
> I do try to re-add the cygautoreconf function and comment out the 
> src_compile function override where possible even in those cases.
> I leave the commented out version in place to document the possibility 
> that re-trying a build without cygautoreconf may fix issues.
> 
> In this case, all such alternatives (cygautoreconf, libtoolize, lndirs) 
> tried either had no effect or broke the builds, which as I said, seem to 
> have all the autoconf and automake files pre-generated, so that cygconf 
> and cygmake should work, given a functional libtool.
> 
> I have also tried to rebuild libtool from sources to pick up updates, 
> but that cygport build no longer even generates a Makefile!
> However I notice that the tar contains a slew of .file temporaries that 
> may be messing up that build.

Only approach that worked was to write a script to update 
/usr/bin/libtool to latest /usr/lib/gcc/$HOSTTYPE-*-$OSTYPE/[0-9]* path, 
add to SRC_URI, and run at the start of src_compile:

https://cygwin.com/git/?p=git/cygwin-packages/ncurses.git;a=tree;hb=playground

https://cygwin.com/cgi-bin2/jobs.cgi?id=3533&srcpkg=ncurses&status=succeeded&user=Brian+Inglis

https://github.com/cygwin/scallywag/actions/runs/1459727318

https://github.com/cygwin/scallywag/suites/4351117248/logs?attempt=1

I will make this an ITA to update ncurses if there are no better 
alternatives suggested to the unconventional approach.
I will then look at how to build the mingw64-*86*-ncurses versions and 
ITA those.

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

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

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