Re: glibc cvs and crosstools

[Dan Kegel <dank at kegel dot com>]

Dara Hazeghi wrote:
> using the latest crosstools with the latest glibc from
> cvs, I've hit a little snafu. When building libgcc
> (the first time) on any target, I get:
>
> /tmp/mainline/objdir/gcc/xgcc ...
>    -c ../../gcc/gcc/crtstuff.c -DCRT_END  -o crtend.o
> In file included from ../../gcc/gcc/tsystem.h:75,
>                  from ../../gcc/gcc/crtstuff.c:62:
> /tmp/dara/x86_64-linux//x86_64-linux/include/stdio.h:138:28:
> bits/stdio_lim.h: No such file or directory
>
> (this happens for other targets too). Solution is
> to...
> cp bits/stdio_lim.h $PREFIX/$TARGET/include/bits
>
> after the initial glibc header installation.

Hmm, that sounds an awful lot like http://gcc.gnu.org/PR8180
Are you sure it isn't fixed by
http://www.kegel.com/crosstool/current/gcc-3.4-20030813-patches/gcc-3.4-without-headers.patch
?
- Dan

--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com