Re: dir.h and compiling gcc 2.95.2 again (Fixed!)

[rmang at ibm dot net]

Thanks to everyone for their help on this issue. I finally found the 
culprit, and in the process learned a lot about glibc2 and gcc. I had 
a gcc dirent.h in the gcc-lib path, which gcc was finding before the 
glibc2 file /usr/include/dirent.h The gcc one is not glibc2 compliant 
(as I compiled gcc under libc5 before upgrading) so this was 
causing the problem. Removing this file seemed to do the trick. 
The gcc -v tipped me off :)

Thanks again!

Rob Mangiafico

> On Thu, May 25, 2000 at 09:43:51PM -0400, rmang@ibm.net wrote:
> > It seems that I cannot recompile gcc with gcc2.95.2 and glibc2 
> > with my system. I am still getting these errors related to not beign 
> > able to detect dir.h and dirent.h. dir.h is included in the .c file, but I 
> > still get this error:
> > ---
> > /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../binutils/bfd -I. -D_GNU_SOURCE   -DTRAD_CORE   -I. -I../../../binutils/bfd -I../../../binutils/bfd/../include   -g -O2 -c ../../../binutils/bfd/trad-core
> > .c
> > gcc -DHAVE_CONFIG_H -I. -I../../../binutils/bfd -I. -
> > D_GNU_SOURCE -DTRAD_CORE -I. -I../../../binutils/bfd -
> > I../../../binutils/bfd/../include -g -O2 -c ../../../binutils/bfd/trad-core.c
> > In file included from /usr/include/sys/dir.h:24,
> >                  from ../../../binutils/bfd/trad-core.c:29:
> > /usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.2/../../../../i686-pc-
> > linux-gnulibc1/include/dirent.h:30: gnu/types.h: No such file or 
> > directory
> > In file included from /usr/include/sys/dir.h:24,
> >                  from ../../../binutils/bfd/trad-core.c:29:
> > /usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.2/../../../../i686-pc-
> > linux-gnulibc1/include/dirent.h:94: posix1_lim.h: No such file or 
> > directory
> > /usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.2/../../../../i686-pc-
> > linux-gnulibc1/include/dirent.h:104: gnu/types.h: No such file or 
> > directory
> Well, your gcc was targeted to i686-pc-linux-gnulibc1 so it searches
> his headers in /usr/local/i686-pc-linux-gnulibc1 first and you've got
> a mess between libc1 and libc2...
> So you should edit your specs file (gcc --print-file-name=specs) to
> not include this OR if you don't understand how to do it simply rename
> /usr/local/i686-pc-linux-gnulibc1 and the old headers won't be taken...
> 
> Regards, gael
>