X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 4A1D53858288
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1693373797;
	bh=GWVsgv4BlfOujIXNm3/k9mjS5iPXtEIOTD7GQYZA6hY=;
	h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=worzzXlXDnCdpmipuGzg3SB8Z6EfS2B+1jwqLbe2UU+mwX+pcNn5ibqxozwnufwhw
	ZL5aJviBoKZxG2/DrfL3GHgsjyYXoLhRFSZkh1LbZ92fhb9VutU3iR41KbFOWGUJF2
	EDqLJ3eZboO38h/8zMfFsDPwM8+PWEHQ5amwgP7M=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 1EE583858D28
Subject:	Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8
To:	cygwin AT cygwin DOT com
References:	<83C27059-CB24-48F5-AC91-AB0622DF82CD AT Denis-Excoffier DOT org>
	<aa38a12e-875a-bfaf-6427-2f8d05c0bc47 AT maxrnd DOT com>
	<ZOh2lNSnYAJmZqUh AT calimero DOT vinschen DOT de>
	<ff004ecd-0bd7-1886-bf81-88daa6b48f2a AT maxrnd DOT com>
	<ZOoFxp0yvqK3ZWxX AT calimero DOT vinschen DOT de>
Message-ID:	<09b77b09-ea43-15b3-1552-c924d502d2f9@maxrnd.com>
Date:	Tue, 29 Aug 2023 22:36:03 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
	Firefox/52.0 SeaMonkey/2.49.4
MIME-Version:	1.0
In-Reply-To:	<ZOoFxp0yvqK3ZWxX@calimero.vinschen.de>
X-Spam-Status:	No, score=-2.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, SPF_HELO_NONE,
	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.30
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>
From:	Mark Geisert via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Mark Geisert <mark AT maxrnd 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>

Corinna Vinschen via Cygwin wrote:
> On Aug 25 22:50, Mark Geisert via Cygwin wrote:
>> Hi Corinna,
>>
>> Corinna Vinschen via Cygwin wrote:
>>> On Aug 24 14:39, Mark Geisert via Cygwin wrote:
>>>> Denis Excoffier via Cygwin wrote:
>>>>> Hello,
>>>>> When i try to compile coreutils-9.3 under cygwin-3.4.8 i get the following error messages (see below).
>>>>> There seems to be a kind of loop in the hierarchy of #includes.
>>>>> Moreover, with cygwin-3.4.7, this is ok. Also, if under cygwin-3.4.8 i remove the 2 #includes from /usr/include/sys/cpuset.h,
>>>>> this is also ok.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Denis Excoffier.
>>>>>
>> [...compilation log excerpt elided here...]
>>>
>>> Usually it's easily fixable. There's typically no loop because
>>> of the guards, e.g.
>>>
>>>     #ifndef _SYS_CPUSET_H_
>>>     #define _SYS_CPUSET_H_
>>>
>>> but some guarding can have side effects.
>>>
>>> However, somebody needs to come up *at least* with a simple reproducer.
>>
>> It can be reproduced by running 'cygport coreutils.cygport build' in a
>> prep'd coreutils source directory e.g. /usr/src/coreutils-9.0-1.src .
>> Excerpt follows:
> 
> This is not what I meant.  A simple reproducer is ideally a piece of
> C code which shows ;the problem with a minimum of code.  In this case,
> a pice of C code with the #includes required to reproduce the compiler
> failing is what I'm looking for.
> 
>> I guess it's the include search order that has ./lib/stdlib.h being included
>> from sys/cpuset.h rather than the "<stdlib.h>" coded there.
> 
> That should break including any other header file, too, which includes
> <stdlib.h>.  Why does it only break sys/cpuset.h?
> 
>> I'm not familiar with building coreutils.  But it seems something about the
>> new #includes added to sys/cpuset.h have upset coreutils' build magic.  My
>> offer to replace the two problematic #includes with two explicit extern
>> statements still stands ;-).
> 
> Sorry, but this is not the right thing to do to fix such an issue.

Agreed.  Also, given the locus of this issue, coding an STC is problematic.  I'm 
taking this coreutils build issue to the cygwin-apps ML for further discussion.

..mark

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