This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Cross compiling
- From: "Albert F. Niessner" <Al dot Niessner at jpl dot nasa dot gov>
- To: list gcc <gcc-help at gcc dot gnu dot org>
- Date: 27 Feb 2003 14:24:53 -0500
- Subject: Cross compiling
How do I tell the configure script to use certain flags during target
compilations?
Host: i686-pc-linux-gnu (Mandrake 9.0 distro)
Target: powerpc-wrs-vxworks (Tornado 2.2 or VxWorks 5.5)
binutils: 2.13.2 (first in $PATH)
gcc: 3.2.2
When I compile it stops at libgcc because __CPU__ and __CPU_FAMILY__ are
not defined. I modified the gcc/Makefile to get that directory to finish
compile and make sure I understood the fix. It works, but then libiberty
and other directories fail -- not all that surprising. So, I then ran
'../gcc-3.2.2/configure --help' looking for help on what flags,
switches, or environment variables I could use to set it at
configuration time so that all of the Makefiles came out right.
According to the help message, there are none. Being somewhat familiar
with autoconf -- I have written a few configure.ac's -- I decided to
poke around and see if there was anything helpful in
gcc-3.2.2/configure.in. Other than discovering FLAGS_FOR_TARGET seems to
be the most appropriate variable to control, it was a total bust. All of
this ultimately leads to the question of:
How do I tell the configure script to use certain flags during target
compilations?
Thanks for any and all help in advance.
Al Niessner