Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: Zhenfeng.Zhao@windriver.com,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] package-index: inherit pythonnative
Date: Wed, 8 Aug 2012 16:29:14 +0800	[thread overview]
Message-ID: <5022235A.9060302@windriver.com> (raw)
In-Reply-To: <50221C2A.5010303@windriver.com>



On 08/08/2012 03:58 PM, Robert Yang wrote:
>
>
> On 08/08/2012 12:57 AM, Richard Purdie wrote:
>> On Mon, 2012-08-06 at 11:29 +0200, Martin Jansa wrote:
>>> On Tue, Jul 24, 2012 at 11:49:52AM +0100, Richard Purdie wrote:
>>>> On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
>>>>> The native python binary has been moved from usr/bin/python to
>>>>> usr/bin/python-native/python, the recipe which needs python-native
>>>>> should "inherit pythonnative", otherwise there would be errors when the
>>>>> python script runs.
>>>>>
>>>>> [YOCTO #2822]
>>>>>
>>>>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>>>>> ---
>>>>>   meta/recipes-core/meta/package-index.bb |    2 ++
>>>>>   1 files changed, 2 insertions(+), 0 deletions(-)
>>>>
>>>> Which part of this recipe needs python-native? Shouldn't scripts which
>>>> need pythonnative be using the path to the python interpreter
>>>> explicitly?
>>>
>>> This fixes my opkg-utils related issues too
>>> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026333.html
>>>
>>> The problem is that with pythonnative in opkg-utils it's still using
>>> #!/usr/bin/env python
>>> in tmp-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index
>>>
>>> And when python-index executes this:
>>> | + [ -e
>>> /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/ ]
>>> | + touch
>>> /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/Packages
>>> | + flock
>>> /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/Packages.flock
>>> -c opkg-make-index -r
>>> /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/Packages
>>> -p
>>> /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/Packages
>>> -m /var/lib/jenkins/jobs/shr-core/workspace/shr-core/tmp-eglibc/deploy/ipk/
>>> | Traceback (most recent call last):
>>>
>>> It depends on PATH of package-index not opkg-utils.
>>
>> I think the right fix here is to remove the PYTHONPATH line in
>> package-index.bb. We should no longer need that and that should fix the
>> problems but its going to be a while before I can test this on a system
>> showing the problem.
>>
>
> Hi Richard
>
> I'd like to remove the PYTHONPATH and started testing package_rpm, package_deb
> pacakge_ipk now (meta-toolchain-sdk and core-image-sato), I will send the
> the patch if the testing is ok (tomorrow).
>

Just noticed that it has been removed after a 'git pull'

// Robert


> // Robert
>
>> Cheers,
>>
>> Richard
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>




      reply	other threads:[~2012-08-08  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 10:19 [PATCH 0/1] package-index: inherit pythonnative Robert Yang
2012-07-24 10:19 ` [PATCH 1/1] " Robert Yang
2012-07-24 10:49   ` Richard Purdie
2012-07-25  3:31     ` Robert Yang
2012-07-27  1:18     ` Robert Yang
2012-07-27 10:32       ` Robert Yang
2012-08-06  9:29     ` Martin Jansa
2012-08-07 16:57       ` Richard Purdie
2012-08-08  7:58         ` Robert Yang
2012-08-08  8:29           ` Robert Yang [this message]

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=5022235A.9060302@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.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