Message-ID: <4F42CFD0.8020204@bellsouth.net>
Date: Mon, 20 Feb 2012 16:57:20 -0600
From: Robert Miles <robertmiles@bellsouth.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@cygwin.com
CC: JonY <jon_y@users.sourceforge.net>
Subject: Re: Issues with stdio.h
References: <CAGHJv4e-Zbqqg-9um+viGKHuajnZdr7AjyXeh16c7A__Lm+V4A@mail.gmail.com> <20120220002507.GA16123@ednor.casa.cgf.cx> <4F42BDAE.50006@towo.net> <4F42C537.2060308@users.sourceforge.net>
In-Reply-To: <4F42C537.2060308@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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