From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corinna@sourceware.org>
Received: by sourceware.org (Postfix, from userid 2155)
	id 8F9033858C2C; Sat, 26 Aug 2023 14:01:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8F9033858C2C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1693058504;
	bh=7mEfQccbi7+9V6UKZo06Cq2A93uyrj8XCwM8eg3mzJg=;
	h=Date:From:To:Subject:Reply-To:References:In-Reply-To:From;
	b=uW1Dl8GffN+05HrXddQYArEe+vOuTyd7l8i4B3d6mSVaPfPKy0nnAx8TbkYQaRWIO
	 6ycuunsTMfpET4R+ku+YXJqhw6sRXitVI6fr9J9Iu1xPo3BoLZbddUGmMYeXS8ulqa
	 WdO3H/44b7FfH90HElq7azf0fuX0u4Y1KLScdJZA=
Received: by calimero.vinschen.de (Postfix, from userid 500)
	id B3775A80CAB; Sat, 26 Aug 2023 16:01:42 +0200 (CEST)
Date: Sat, 26 Aug 2023 16:01:42 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: can't compile coreutils-9.3 any more after upgrade to
 cygwin-3.4.8
Message-ID: <ZOoFxp0yvqK3ZWxX@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <83C27059-CB24-48F5-AC91-AB0622DF82CD@Denis-Excoffier.org>
 <aa38a12e-875a-bfaf-6427-2f8d05c0bc47@maxrnd.com>
 <ZOh2lNSnYAJmZqUh@calimero.vinschen.de>
 <ff004ecd-0bd7-1886-bf81-88daa6b48f2a@maxrnd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <ff004ecd-0bd7-1886-bf81-88daa6b48f2a@maxrnd.com>
List-Id: <cygwin.cygwin.com>

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.


Corinna