🚀 go-pugleaf

>./xgcc -B./ -DCROSS_COMPILE -DIN_GCC   -g    -c ./cross-test.c
>./xgcc -B./ -DCROSS_COMPILE -DIN_GCC   -g cross-test.o -o cross-test
>/usr/local/sun3/bin/gld: Can't open crt0.o
>collect: ld returned 1 exit status
>make: *** [cross-test] Error 1
># 
>
>Can anybody tell me what this is about and how to fix it?

You have to copy crt0.o (C startup code) from Sun3 to
(either where cross gld expects objects [or where ./xgcc is located, I
am not sure about this] for the cross compilation test.

Aside from crt0.o, it will look for libc.a libg.a and a few other
objects files. You will find them in /lib/ (or /usr/lib it is a
symlink.).

I wish GCC/BINUTILS/GAS documents mentions these things in the
documentation. (I know that it is impossible to write a comprehensive
cross development build documents unless the host and target is
clearly defined. However, using, say, a Sparc host and Sun3 target as
an example  and showing the details of which header files to copy to
where(!) and which objects and library files to copy to where(again!)
would be very, very useful. 

At least I have found out 2.4.5 texinfo of GCC contains much better
description about cross compilation than older ones.
I think a good example (sparc to  sun3) may be a great boost for
acceptance of gcc as cross development tool.


 Chiaki Ishikawa,  Personal Media Corp.,  MY Bldg, 1-7-7 Hiratsuka,
 Shinagawa, Tokyo 142, JAPAN. FAX:+81-3-5702-0359, Phone:+81-3-5702-0351
 UUNET: ishikawa@personal-media.co.jp