This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-3.2: config problem
- From: Doru Carastan <doru dot carastan at mvista dot com>
- To: gcc at gcc dot gnu dot org
- Cc: Michael Eager <eager at mvista dot com>
- Date: Tue, 30 Sep 2003 10:36:37 -0700
- Subject: Re: gcc-3.2: config problem
- Organization: MontaVista Software, Inc.
I have found that configure sets GCC_FOR_TARGET to the cross-compiler I
use in the root Makefile.
GCC_FOR_TARGET = i686-pc-cygwin-gcc
Then gcc/Makefile is using it to create the spec file
specs: xgcc$(exeext)
$(GCC_FOR_TARGET) -dumpspecs > tmp-specs
mv tmp-specs specs
and obviously the spec file defines:
*cross_compile:
1
Which IMO is plain wrong considering that the configure line was
"$r/src/$gcc/configure" --build=i686-pc-linux-gnu \
--host=i686-pc-cygwin --target=i686-pc-cygwin \
--prefix=/usr --includedir=/nonexistent/include \
--enable-languages=c,c++ \
--enable-threads=posix \
--with-system-zlib \
--enable-nls \
--without-included-gettext \
--disable-version-specific-runtime-libs \
--enable-shared \
--enable-haifa \
--enable-interpreter
Can someone shed some light here? Why GCC_FOR_TARGET is not left as
defined in the Makefile?
GCC_FOR_TARGET = ./xgcc -B./ -B$(build_tooldir)/bin/ -isystem
$(build_tooldir)/include -isystem $(build_tooldir)/sys-include
--
Doru Carastan
*\\\///* WinHost Contractor
||\\//|| 408-992-4497
|||\/||| doru.carastan@mvista.com