[OE-core] [PATCH] gcc: Add ability for tune files to pass in configure options to gcc

[Kumar Gala]

On Aug 1, 2011, at 9:30 AM, Phil Blundell wrote:

> On Mon, 2011-08-01 at 09:21 -0500, Kumar Gala wrote:
>> Added a ${GCC_EXTRA_OECONF} to the the building up of gcc's
>> ${EXTRA_OECONF}.  This is similar to what we have in the glibc recipe
>> files.
>> 
>> This allows for a tune file to add something like:
>> 
>> GCC_EXTRA_OECONF += "--with-cpu=e5500"
>> 
>> If needed.
>> 
>> Signed-off-by: Kumar Gala <galak at kernel.crashing.org>
> 
> Why is that desirable?  From the looks of that patch it will affect
> gcc-cross as well as target gcc and, if you're going to do this, I think
> you need to find some way to disambiguate the resulting compilers.
> Otherwise there is going to be no way to predict what options ${CC} was
> built with.

Its desirable to get a consistent set of tools.  For example it means the cross toolchain in an ADT will target the given processor it was built with w/o having to explicit set flags to gcc.

Additionally, it might be useful for building multilib gcc on powerpc that seems to need --with-cpu-32 --with-cpu-64.

Not sure I understand the statement about disambiguate the resulting compilers, on PPC where I intend to utilize this we'd have the toolchains already named something like:

ppc64e5500-poky-linux-gcc

> Even for the on-target gcc case, if you are going to start putting
> MACHINE-specific variables into the configure commandline then you need
> to make sure that the output packages have an appropriate Architecture.
> I don't think that's going to be the case at the moment.

I'm open to solutions to my problem, but need to find someway to pass '--with-cpu=' to configure.

- k