Re: [PATCH 1/1] python-native: Fix a compiler finding issue

[Tom Rini <tom_rini@mentor.com>]

On 07/28/2011 06:15 PM, Mei, Lei wrote:
> 
> 
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Tom Rini
>> Sent: Thursday, July 28, 2011 11:09 PM
>> To: openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH 1/1] python-native: Fix a compiler finding issue
>>
>> On 07/28/2011 12:20 AM, Mei Lei wrote:
>>> The CC variable sometimes add option information after compiler name, but
>> python can't get the real compiler name if those information added.
>>> Fix this issue by dropping the option information when finding compiler name.
>>>
>>> Signed-off-by: Mei Lei <lei.mei@intel.com>
>>
>> I think this is going to cause problems when you must pass flags to gcc
>> to have it work, eg 'gcc -m64'.
> 
> This patch fixed your worried issue.
> The CC variable, sometimes like:  "x86_64-poky-linux-gcc -m64 --sysroot=/${TMPDIR}/sysroots/qemux86-64", contains flags information. 
> This will lead to wrong compiler name "qemux86-64" rather than "x86_64-poky-linux-gcc" when python finding the compiler name, so add this patch to find the real gcc name.

No, what I'm saying is I have a compiler that must be invoked as 'gcc
-m64' (which is what BUILD_CC is).  So, I think after saying that, the
right answer is to modify python to read the OE-specific BUILD_CC variable.

-- 
Tom Rini
Mentor Graphics Corporation