From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kai Ruottu To: munroe@csworks.com Cc: crossgcc@sourceware.cygnus.com Subject: Re: Trying to build a cross compiler from linux to netbsd... Date: Wed, 03 Jan 2001 04:33:00 -0000 Message-id: <3A531542.7575179A@luukku.com> References: <3A5293AF.CC95CA6E@csworks.com> X-SW-Source: 2001-01/msg00011.html Dick Munroe wrote: > > using egcs 1.0.3a (other compilers aren't an option, unfortunately, the > vendor says that this is the only one guaranteed to work). Anyway, we > have Linux boxes and need to cross compile to Netbsd (more particularly, > i386 a.out format executables). The following is one attempt: > > Binutils builds with: > > ../binutils-2.10.1/configure --host=i686-pc-linux-gnu --target=i386-aout > --prefix=/home/usr/local Why 'i386-aout' when your target is 'i386-netbsd' ? The 'i386-aout' is for a generic embedded system using the 'aout' object format and the format used in the NetBSD libs most probably isn't the same... ------------------------- clip ---------------------------------- F:\usr\local\i486-netbsd\bin>ld -V GNU ld version 2.9.1 (with BFD 2.9.1) Supported emulations: i386nbsd F:\usr\local\i486-netbsd\bin>ld --help Usage: ld [options] file... ld: supported targets: a.out-i386-netbsd a.out-i386-bsd srec symbolsrec tekhex binary ihex ld: supported emulations: i386nbsd F:\usr\local\i486-netbsd\lib>..\bin\nm crt0.o U __DYNAMIC 000007cc D ___progname 000007d0 D ___ps_strings 00000054 T ___start U _atexit 000006e8 T _dlclose 00000730 T _dlctl 00000770 T _dlerror 000006c4 T _dlopen 0000070c T _dlsym 00000004 C _environ 00000004 C _errno U _exit U _main U _strerror 00000000 T start ------------------------- clip ---------------------------------- At least the shared libs, to which the '__DYNAMIC' in the startup hints, can be totally unsupported with 'i386-aout'... So my primary suggestion would be to use the right target name... For how to pre-install and handle the target libs & headers, I'll refer to my second message about this subject. Cheers, Kai ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kai Ruottu To: munroe@csworks.com Cc: crossgcc@sourceware.cygnus.com Subject: Re: Trying to build a cross compiler from linux to netbsd... Date: Sun, 01 Apr 2001 00:00:00 -0000 Message-ID: <3A531542.7575179A@luukku.com> References: <3A5293AF.CC95CA6E@csworks.com> X-SW-Source: 2001-q1/msg00011.html Message-ID: <20010401000000.E-wrP5SVSLCHJMsk6rZD5xzvPUnUgtn5LyU6p2n3_A8@z> Dick Munroe wrote: > > using egcs 1.0.3a (other compilers aren't an option, unfortunately, the > vendor says that this is the only one guaranteed to work). Anyway, we > have Linux boxes and need to cross compile to Netbsd (more particularly, > i386 a.out format executables). The following is one attempt: > > Binutils builds with: > > ../binutils-2.10.1/configure --host=i686-pc-linux-gnu --target=i386-aout > --prefix=/home/usr/local Why 'i386-aout' when your target is 'i386-netbsd' ? The 'i386-aout' is for a generic embedded system using the 'aout' object format and the format used in the NetBSD libs most probably isn't the same... ------------------------- clip ---------------------------------- F:\usr\local\i486-netbsd\bin>ld -V GNU ld version 2.9.1 (with BFD 2.9.1) Supported emulations: i386nbsd F:\usr\local\i486-netbsd\bin>ld --help Usage: ld [options] file... ld: supported targets: a.out-i386-netbsd a.out-i386-bsd srec symbolsrec tekhex binary ihex ld: supported emulations: i386nbsd F:\usr\local\i486-netbsd\lib>..\bin\nm crt0.o U __DYNAMIC 000007cc D ___progname 000007d0 D ___ps_strings 00000054 T ___start U _atexit 000006e8 T _dlclose 00000730 T _dlctl 00000770 T _dlerror 000006c4 T _dlopen 0000070c T _dlsym 00000004 C _environ 00000004 C _errno U _exit U _main U _strerror 00000000 T start ------------------------- clip ---------------------------------- At least the shared libs, to which the '__DYNAMIC' in the startup hints, can be totally unsupported with 'i386-aout'... So my primary suggestion would be to use the right target name... For how to pre-install and handle the target libs & headers, I'll refer to my second message about this subject. Cheers, Kai ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com