X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE
X-Spam-Check-By:	sourceware.org
X-Yahoo-SMTP:	QDdxPgyswBCK2bx7SNYDilAqkd6GnSZOMbWnqiDrvOLygeouYdY-
Message-ID:	<4F42CFD0.8020204@bellsouth.net>
Date:	Mon, 20 Feb 2012 16:57:20 -0600
From:	Robert Miles <robertmiles AT bellsouth DOT net>
User-Agent:	Mozilla/5.0 (Windows NT 6.0; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
CC:	JonY <jon_y AT users DOT sourceforge DOT net>
Subject:	Re: Issues with stdio.h
References:	<CAGHJv4e-Zbqqg-9um+viGKHuajnZdr7AjyXeh16c7A__Lm+V4A AT mail DOT gmail DOT com> <20120220002507 DOT GA16123 AT ednor DOT casa DOT cgf DOT cx> <4F42BDAE DOT 50006 AT towo DOT net> <4F42C537 DOT 2060308 AT users DOT sourceforge DOT net>
In-Reply-To:	<4F42C537.2060308@users.sourceforge.net>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 2/20/2012 4:12 PM, JonY wrote:
> On 2/21/2012 05:39, Thomas Wolff wrote:
>> Am 20.02.2012 01:25, schrieb Christopher Faylor:
>>> On Sun, Feb 19, 2012 at 07:07:04PM -0500, Chris Sutcliffe wrote:
>>>> ...
>>>> /usr/include/stdio.h:34:20: fatal error: stddef.h: No such file or
>>>> directory
>>> stddef.h comes from the gcc4-core package.  It's located in:
>>>
>>> usr/lib/gcc/i686-pc-cygwin/4.5.3/include/stddef.h
>>>
>>> and should be found automatically by the compiler.
>> I think it's a weird setup that an include file referred from
>> /usr/include is not found in that location but well hidden in
>> installation-specific directories. Not the usual setup anyway. Also
>> uncomfortable for people who want to check include files manually.
>> Please consider to change this (gcc maintainer?).
>> Thomas
>>
> So how are you supposed to use headers provided by the compiler anyway
> without going into that compiler specific directory?
>
Why not put a stddef.h file into /user/include that includes comments 
showing
where to find the compiler-specific stddef.h files?  And if putting it 
there makes
the compiler try to use it instead of the compiler-specific one, also 
add the code
needed to tell the compiler to include the compiler-specific one, after 
checking
which compiler is currently in use.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -