[OE-core] [PATCH 1/1] package-index: inherit pythonnative

[Richard Purdie]

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 at 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.

Cheers,

Richard