Re: extend crosstool.sh to allow gcc4 as native compiler?

["Arno Schuring" <aelschuring at hotmail dot com>]

> > > >   it seems that, at the moment, crosstool.sh is pretty well hardcoded
> > > > to use "gcc" only:
> > > >
> > > >   CC=gcc \
> > > >
> > > > that sort of thing.  would it be a big deal to make that a variable?
> > >
> > >
> > > Give it a try, see what happens.  Pick some nice unique variable name, 
> > > though.
> >
> > Would CC be considered unique enough? I can't think of a reason not to 
> > use CC itself. crosstool should unset it for crossbuilds, of course, but 
> > that would apply now as well. Then again, it's late here and I should 
> > probably get some sleep.
>
> Hrmph.  Well, maybe.    I must say, it'd be more than a fulltime
> job to get all this right... miracle it all works at all...
> - Dan

Whoops. No offense intended. Crosstool already overrides CC when doing the 
glibc crossbuild, even though I did not bother to check that before. I did 
not (mean to) imply that crosstool missed a point, I meant that using CC 
would introduce no problems at all.

As far as I can see in the script, if you set CC before running crosstool, 
all installed tools will be compiled with $CC. Only the glibc headers 
(CC=gcc) and the intermediate programs needed by glibc (BUILD_CC=gcc) are 
not built using $CC. This may not even introduce problems, but for 
completeness sake, you can remedy it using shell expansion:

<        CC=gcc \
===
>        CC=${CC:-gcc} \

and

<    BUILD_CC=gcc [...]
===
>    BUILD_CC=${CC:-gcc} [...]

(patch added, though as of now untested)

I'm doing a test-run with these settings and modified CC now, will keep you 
posted.


Arno

 np: Chroma Key - Even The Waves

Attachment: crosstool-useCC.diff
Description: Binary data

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