Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Lu Chong <Chong.Lu@windriver.com>
To: Saul Wold <sgw@linux.intel.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] python-native: export some environment variables
Date: Tue, 25 Feb 2014 10:50:10 +0800	[thread overview]
Message-ID: <530C04E2.8060400@windriver.com> (raw)
In-Reply-To: <530B54B0.8090304@linux.intel.com>


On 02/24/2014 10:18 PM, Saul Wold wrote:
> On 02/22/2014 07:54 AM, Chong Lu wrote:
>> Need to export these environment variables for python-config to work.
>>
> Can you clariy further as to what's broken?  Has this not been working 
> in the past, or is this a new test of somekine that we are failing?
>
> Sau!
>


checking for python script directory... Traceback (most recent call last):
   File "<string>", line 22, in <module>
   File 
"/yocto/build/qemux86-64/tmp/sysroots/x86_64-linux/usr/lib/python2.7/distutils/sysconfig.py", 
line 22, in <module>
     PREFIX = os.path.normpath(sys.prefix).replace( 
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
TypeError: expected a character buffer object
${libdir}/python2.7/site-packages
checking for python extension module directory... Traceback (most recent 
call last):
   File "<string>", line 22, in <module>
   File 
"/yocto/build/qemux86-64/tmp/sysroots/x86_64-linux/usr/lib/python2.7/distutils/sysconfig.py", 
line 22, in <module>
     PREFIX = os.path.normpath(sys.prefix).replace( 
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
TypeError: expected a character buffer object

Above error comes from some packages' do_configure log.
This error doesn't block building.
Some packages export above env variables in bb file, but someone not.
So I think these env variables should be exported in bbclass file.

Best Regards
Chong


>> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
>> ---
>>   meta/classes/pythonnative.bbclass |    4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/meta/classes/pythonnative.bbclass 
>> b/meta/classes/pythonnative.bbclass
>> index fdd22bb..58a5b5c 100644
>> --- a/meta/classes/pythonnative.bbclass
>> +++ b/meta/classes/pythonnative.bbclass
>> @@ -4,3 +4,7 @@ inherit python-dir
>> PYTHON="${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN}"
>>   EXTRANATIVEPATH += "${PYTHON_PN}-native"
>>   DEPENDS += " ${PYTHON_PN}-native "
>> +export STAGING_INCDIR
>> +export STAGING_LIBDIR
>> +export BUILD_SYS
>> +export HOST_SYS
>>
>
>



  reply	other threads:[~2014-02-25  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22  5:54 [PATCH] python-native: export some environment variables Chong Lu
2014-02-24 14:18 ` Saul Wold
2014-02-25  2:50   ` Lu Chong [this message]
2014-03-24  6:45     ` Chong Lu

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=530C04E2.8060400@windriver.com \
    --to=chong.lu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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