This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Problems making a cross-compiler
- From: Kai Ruottu <karuottu at mbnet dot fi>
- To: David Fernandez <dfernandez at cct dot co dot uk>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Fri, 17 Feb 2006 13:53:37 +0200
- Subject: Re: Problems making a cross-compiler
- References: <1140172099.11169.30.camel@software.cct.co.uk>
David Fernandez kirjoitti:
/usr/src/redhat/BUILD/gcc-4.0.2/configure --prefix=/usr/local/i686-pc-msdosdjgpp --enable-checking=release --disable-threads --disable-libunwind-exceptions --enable-target-optspace --with-system-zlib --enable-__cxa_atexit --enable-languages="c,c++" --host=i386-redhat-linux --target=i686-pc-msdosdjgpp
Are these options really required with the DJGPP2 targeted GCC ? With
the Linux target the '--enable-__cxa_atexit' may be motivated but does
the DJGPP2
target C library support this feature? If all there really are
required, things are ok. But somehow this reminds me about people once
putting all kind of commands
into their CONFIG.SYS and AUTOEXEC.BAT only because their friends told
those being "useful"... But nobody seemed to understand what they were
and why
they must be put there. The configure example in the GCC manual:
"configure --target=my_chosen_target" for a crosscompiler could be a
better model for the
configure command than one seen with 'gcc -v' with the native Linux GCC...