problems with installation

Joshua Pincus pncu_ss@uhura.cc.rochester.edu
Thu Feb 4 15:33:00 GMT 1999


Hi,

I'm trying to make a cross compiler on a SPARC Solaris 2 system for a 
FreeBSD 2.2.7 system.  

I installed binutils on the SPARC with i386-unknown-freebsd2.2.7 as the 
target.  I compiled libgcc1.a on the FreeBSD machine natively.  I compiled
gcc-2.8.1 on the SPARC with target=i386-unknown-freebsd2.2.7, 
--with-gnu-as, and --with-gnu-ld.  

The resulting compiler reports the following errors when I try to compile 
anything:

quark:/var/tmp/compiler/newlib-1.8.1 787> ./configure --target=i386-unknown-freebsd2.2.7 --prefix=/tmp/cross -v
Configuring for a sparc-sun-solaris2.6 host.
Created "Makefile" in /var/tmp/compiler/newlib-1.8.1 using "mh-frag"
/tmp/cross/i386-unknown-freebsd2.2.7/lib/crt0.o(.text+0x421): undefined
reference to `_DYNAMIC'
/tmp/cross/i386-unknown-freebsd2.2.7/lib/crt0.o(.text+0x3c2): undefined
reference to `_DYNAMIC'
/tmp/cross/i386-unknown-freebsd2.2.7/lib/crt0.o(.text+0x57): undefined
reference to `_DYNAMIC'
/tmp/cross/i386-unknown-freebsd2.2.7/lib/libc.a(atexit.o)(.text+0x30):
undefined reference to `sbrk'
/tmp/cross/i386-unknown-freebsd2.2.7/lib/libc.a(exit.o)(.text+0x36): undefined
reference to `_exit'
*** The command '/tmp/cross/bin/i386-unknown-freebsd2.2.7-gcc -o conftest -g
conftest.c' failed.
*** You must set the environment variable CC to a working compiler.

I could not configure newlib without the crt0.o and libc.a files from the
FreeBSD box, so I ftp'ed them over and installed them in $prefix/$target/lib.

What am I doing wrong???  Why can't I use the C libraries that were compiled on
the native machine? 

Thanks,
JP
-- 
Joshua Pincus
UNIX Technical Assistant
Rm. 44 
TR   12:00 - 3:00
MF    1:00 - 3:00
_______________________________________________
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
_______________________________________________
To remove yourself from the crossgcc list, send
mail to crossgcc-request@cygnus.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.



More information about the crossgcc mailing list