Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] python-native: Fix	a	compiler	finding	issue
Date: Fri, 29 Jul 2011 08:28:51 -0700	[thread overview]
Message-ID: <4E32D1B3.4010707@mentor.com> (raw)
In-Reply-To: <749B9D3DBF0F054390025D9EAFF47F2212D0FCC70E@shsmsx501.ccr.corp.intel.com>

On 07/28/2011 11:58 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: Friday, July 29, 2011 9:44 AM
>> To: openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH 1/1] python-native: Fix a compiler finding issue
>>
>> 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.
> 
> 
> I think I didn't describe this patch exactly before.
> 
> This patch is only for function runtime_library_dir_option, this function is to detect which platform we are running and what compiler we used, then decide what option information should be passed to compiler.
> 
> By default, our cross-compiler's name be recognized as "qemux86" rather than " x86_64-poky-linux-gcc" in this function, this is wrong, this will induce a wrong option information passed to x86_64-poky-linux-gcc and block the compile process.
> 
> And function runtime_library_dir_option only return the option information, so didn't influence compiler name in global.
> 
> By the way, I think BUILD_CC is host compiler name, not for target.

You're patching python-native, not python, which means the host python
and not the target python.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-07-29 15:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28  7:20 [PATCH 0/1]python-native: Fix a compiler finding issue Mei Lei
2011-07-28  7:20 ` [PATCH 1/1] python-native: " Mei Lei
2011-07-28 15:08   ` Tom Rini
2011-07-29  1:15     ` Mei, Lei
2011-07-29  1:43       ` Tom Rini
2011-07-29  6:58         ` Mei, Lei
2011-07-29 15:28           ` Tom Rini [this message]
2011-08-01 12:41             ` Mei, Lei
2011-08-01 17:27               ` Khem Raj
2011-08-02  3:08                 ` Mei, Lei
2011-08-10 23:28 ` [PATCH 0/1]python-native: " Saul Wold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E32D1B3.4010707@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox