Re: specifying native compiler

[Khem Raj <khem at mvista dot com>]

David Karlton said the following on 01/03/2006 11:26 AM:

> Dan Kegel wrote:
>
> > On 1/3/06, Dave Korn <dave.korn@artimi.com> wrote:
> >
> > > David Karlton wrote:
> > >
> > > > I have crosstool-0.38 (kegel.com/crosstool), and want to build using a
> > > > different gcc compiler that I have on my local machine. Many of the
> > > > scripts seem to default to CC=gcc.  Is there one meta-override so I
> > > > could specify a different native compiler?
> > >
> > >
> > >  If I understand what you're asking right, and if I remember 
> > > correctly, you
> > > should just be able to write
> > >
> > > CC=<your_gcc_version> script.name [-options]
> >
> >
> >
> > Nope, sorry, crosstool.sh doesn't obey that convention.
> > There's even a hardcoded line or two like
> >   CC=gcc ...
> >   BUILD_CC=gcc
> > at one point in it.
> >
> > I'd say create a fake gcc script that invokes the desired compiler,
> > and put that on your path.   Alternately, modify crosstool.sh to 
> > uniformly
> > use BUILD_CC, and make it easy for users to set that; then submit the
> > change so others can benefit.
> > - Dan
> > p.s. Wow, a three-DK thread!
>
>
> This mean anything to anybody?
>
> /home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/build-gcc-core/gcc/xgcc 
> -B/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/build-gcc-core/gcc/ 
> -B/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/gcc-core-prefix/mipsel-unknown-linux-gnu/bin/ 
> -B/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/gcc-core-prefix/mipsel-unknown-linux-gnu/lib/ 
> -isystem 
> /home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/gcc-core-prefix/mipsel-unknown-linux-gnu/include 
> -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings 
> -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -fPIC -g 
> -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. 
> -I/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/gcc-3.2.3/gcc 
> -I/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/gcc-3.2.3/gcc/. 
> -I/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/gcc-3.2.3/gcc/config 
> -I/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/gcc-3.2.3/gcc/../include 
>  -DL_divdi3 -c 
> /home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/gcc-3.2.3/gcc/libgcc2.c 
> -fexceptions -fnon-call-exceptions -o libgcc/./_divdi3.o
> /tmp/ccQX5bNh.s: Assembler messages:
> /tmp/ccQX5bNh.s:1181: Error: operation combines symbols in different 
> segments
> /tmp/ccQX5bNh.s:1211: Error: operation combines symbols in different 
> segments
> make[2]: *** [libgcc/./_divdi3.o] Error 1
> make[2]: Leaving directory 
> `/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/build-gcc-core/gcc' 
>
> make[1]: *** [libgcc.a] Error 2
> make[1]: Leaving directory 
> `/home/dkarlton/crosstool-0.38/build/mipsel-unknown-linux-gnu/gcc-3.2.3-glibc-2.2.3/build-gcc-core/gcc' 
>
> make: *** [all-gcc] Error 2
>
>
>
> ------
> Want more information?  See the CrossGCC FAQ, 
> http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to 
> crossgcc-unsubscribe@sources.redhat.com
This thread might help
http://sourceware.org/ml/binutils/2005-02/msg00644.html

--
Khem Raj <khem@mvista.com>
MontaVista Software, Inc.
www.mvista.com



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com