This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Issues with stdio.h


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]