Cross Compiler Install questions
Yves Rutschle
y.rutschle@indigovision.com
Thu Jan 18 02:48:00 GMT 2001
[...]
> Now I get the popular error message:
> ....../libgcc2.c:41: stdlib.h: No such file or directory
> ....../libgcc2.c:42: unistd.h: No such file or directory
I think we should make T-shirts with those two lines in the back.
I'd buy a box of them :-)
> I tried to look for documentation for this problem, but the
> only thing I can find is the fix relating to newlib.
> Does anyone know how to handle this problem using glibc?
>
> I searched the glibc source directory and found those two files at:
> /glibc_source/include/stdlib.h
> /glibc_source/stdlib/stdlib.h
> /glibc_source/include/sys/unistd.h
> /glibc_source/indluce/unistd.h
> /glibc_source/posix/sys/unistd.h
> /glibc_source/posix/unistd.h
>
>From my experiments, it's very hard to use the headers of glibc
before compiling glibc, because they have lots of architecture
depedent parts, which will be resolved after configure/compile
of glibc, which you can't do without your crossgcc.
On top of that, if you want a *-linux-gcc, you need to add
configured linux files.
Have a look at http://inkvine.fluff.org/~chris/arm-tools.html
just ignore the parts about ARM-specific patches, and that
should be fine (hopefully).
Good luck!
Yves.
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
More information about the crossgcc
mailing list