Where is stddef.h???

Bill C. Riemers bcr@sanskrit.lz.att.com
Tue Jun 8 06:56:00 GMT 1999


It doesn't really matter what command line I use.  Even:
	gcc -c foo.c
will produce the problem.  It seems the problem is specific to SuSE 6.0 and
SuSE 6.1.  I used VMWARE to build egcs under RH5.2 on the same NFS mounted
partition, /usr/local/OS, and the problem just went away.  So it looks like
SuSE is missing something required for correctly building and installing
egcs.

				Bill


Jeffrey A Law wrote:
> 
>   In message < 375C0208.4747B2AA@sanskrit.lz.att.com >you write:
>   > Hi.  I just installed egcs version 2.91.66 with the following procedure:
>   > In file included from /j9/bcr/Cybrary/Compressor/src/libungif-4.1.0/dgif_li
>   > b.c:20:
>   > /usr/include/sys/types.h:70: warning: No include path in which to find stdd
>   > ef.h
>   > In file included from /j9/bcr/Cybrary/Compressor/src/libungif-4.1.0/dgif_li
>   > b.c:25:
>   > /usr/include/stdlib.h:32: warning: No include path in which to find stddef.
>   > h
>   > In file included from /usr/include/stdlib.h:360,
>   >                  from /j9/bcr/Cybrary/Compressor/src/libungif-4.1.0/dgif_li
>   > b.c:25:
>   > /usr/include/alloca.h:25: warning: No include path in which to find stddef.
>   > h
>   > In file included from /usr/include/libio.h:31,
>   >                  from /usr/include/stdio.h:29,
>   >                  from /j9/bcr/Cybrary/Compressor/src/libungif-4.1.0/dgif_li
>   > b.c:28:
>   > /usr/include/_G_config.h:13: warning: No include path in which to find stdd
>   > ef.h
>   > In file included from /usr/include/stdio.h:29,
>   >                  from /j9/bcr/Cybrary/Compressor/src/libungif-4.1.0/dgif_li
>   > b.c:2
>   >
>   > I've searched the egcs distribution and I can not find a file called stddef
>   > .h.  I've
>   > search my Linux distribution, and the only file I can find call stddef.h is
>   > /usr/include/g++-2.7/std/stddef.h
>   >
>   > This seems way too obvious of a problem for it not to be listed in the FAQ
>   > or list of
>   > known problems, or even a mention in the egcs-bugs archive.  But I can find
>   >  no mention
>   > of where this file is suppose to come from and what it should contain, and
>   > why it is
>   > missing.
> You didn't include the command line which is causing this problem.  GCC
> provides
> its own stddef.h which is should be able to automatically find, unless you
> are somehow overriding the default search paths.
> 
> jeff


More information about the Gcc-bugs mailing list