X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8F4F6385828E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1693058539;
	bh=clTfv4Jyc/nZurjSUpztGY3X8qXM/FEPet4tEFUgxhk=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=Bw8hCTXwj72Cfuq7e6+1qQBaUi2t11eN2KvCPYV4e+vXZMAA6VRJg9x9E0DxfC+YH
	 nt09WDqZeOhj2M6I3sUmX2djwgOtoEis/XeV5Hk9364mn4H2/fumJ3vqzOMpb3axIw
	 KA1A4VKdI4qM4RP/sV6LGl9zfVSxTeZQHctPft3c=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8F9033858C2C
Date: Sat, 26 Aug 2023 16:01:42 +0200
To: cygwin AT cygwin DOT com
Subject: Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8
Message-ID: <ZOoFxp0yvqK3ZWxX@calimero.vinschen.de>
Mail-Followup-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>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <ff004ecd-0bd7-1886-bf81-88daa6b48f2a@maxrnd.com>
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
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: Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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 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

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