Additional information: #error Cannot find a suitable type for FF ECOM_f2cLONGINT

Vermeulen Jan Jan.Vermeulen@siemens.atea.be
Wed Apr 11 23:18:00 GMT 2001


>/src/gcc/gcc-2.95.3-2/gcc/libgcc2.c:41: stdlib.h: No such file or directory
>/src/gcc/gcc-2.95.3-2/gcc/libgcc2.c:42: unistd.h: No such file or directory
>make[3]: *** [libgcc2.a] Error 1
>make[3]: Leaving directory `/tmp/build/gcc/gcc'
>make[2]: *** [stmp-multilib-sub] Error 2
>make[2]: Leaving directory `/tmp/build/gcc/gcc'
>make[1]: *** [stmp-multilib] Error 1
>make[1]: Leaving directory `/tmp/build/gcc/gcc'
>make: *** [all-gcc] Error 2
>make: Leaving directory `/tmp/build/gcc'


I don't know if it will help, but i received this error too.
(many people seem to have this error when compiling cross tool chains)

It has to do with the include files of the library you want to build with.
You can easily solve this by making a symlink in your target directory.

I suggest you read up on the following:
http://sources.redhat.com/ml/crossgcc/2000-q2/msg00195.html

where there is explained how to build crossgcc in a different way than the
manual describes.

I don't know if it can solve your problem 100%, but it's at least worth a 
try.

Gd luck,
Jan

PS: i really suggest to everyone using embedded platforms to use the newlib
library.

------
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