Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] python, python-native: upgrade from 2.6.6 to 2.7.2
Date: Thu, 13 Oct 2011 23:40:48 +0200	[thread overview]
Message-ID: <20111013214048.GA3542@jama.jama.net> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94E0BCEAC0@orsmsx504.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]

On Thu, Oct 13, 2011 at 01:09:15PM -0700, Kamble, Nitin A wrote:
> Martin,
>   I am fixing the python 2.7.2 recipe, and I need to update the generate-manifest-2.7.py script slightly, to get more files included in the python-core package.

great, I was debuging it a bit more today and found out that the problem
seems to be in python-native, because with python-native-2.7.2 when I
try to build old python-2.6.6 it's also tring to link extra modules to
-native libpython2.7 and fails:
/OE/shr-core/tmp/sysroots/x86_64-linux/usr/lib/libpython2.7.so: file not recognized: File format not recognized

but even after comparing sysroots/builddirs/logs from 2.6.6 and 2.7.2 
I still don't see why it picked right libpython2.6 before and now it fails.
I've tried it without multilib support and partially reverted 
changes in patches from 2.6.6 and still it fails :/

btw: there seems to be also issue in runtime
SHR root@gjama ~ $ python -v
Could not find platform independent libraries <prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
# installing zipimport hook
import zipimport # builtin
# installed zipimport hook
ImportError: No module named site
# clear __builtin__._
# clear sys.path
# clear sys.argv
# clear sys.ps1
# clear sys.ps2
# clear sys.exitfunc
# clear sys.exc_type
# clear sys.exc_value
# clear sys.exc_traceback
# clear sys.last_type
# clear sys.last_value
# clear sys.last_traceback
# clear sys.path_hooks
# clear sys.path_importer_cache
# clear sys.meta_path
# clear sys.flags
# clear sys.float_info
# restore sys.stdin
# restore sys.stdout
# restore sys.stderr
# cleanup __main__
# cleanup[1] zipimport
# cleanup[1] signal
# cleanup[1] exceptions
# cleanup[1] _warnings
# cleanup sys
# cleanup __builtin__
# cleanup ints: 5 unfreed ints
# cleanup floats

> BTW how to run this script ? some documentation of it in the script would be useful.

just execute it and it prints manifest, so something like this:
openembedded-core $ scripts/contrib/python/generate-manifest-2.7.py > meta/recipes-devtools/python/python-2.7-manifest.inc

Regards,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2011-10-13 21:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30  1:27 [PATCH 0/4] Recipes upgrades nitin.a.kamble
2011-09-30  1:27 ` [PATCH 1/4] gdb: upgrade from 7.3a to 7.3.1 nitin.a.kamble
2011-09-30  1:27 ` [PATCH 2/4] byacc: upgrade from 20101229 to 20110908 nitin.a.kamble
2011-09-30  1:27 ` [PATCH 3/4] python-dbus: upgrade from 0.83.2 to 0.84.0 nitin.a.kamble
2011-09-30  1:27 ` [PATCH 4/4] python, python-native: upgrade from 2.6.6 to 2.7.2 nitin.a.kamble
2011-09-30 18:37   ` Martin Jansa
2011-09-30 18:38     ` [PATCH] python: update generate-manifest for 2.7 version and regenerate it Martin Jansa
2011-09-30 18:40     ` [PATCH 4/4] python, python-native: upgrade from 2.6.6 to 2.7.2 Kamble, Nitin A
2011-09-30 18:46       ` Martin Jansa
2011-10-01 18:33         ` Martin Jansa
2011-10-02  1:17           ` Kamble, Nitin A
2011-10-13 20:09           ` Kamble, Nitin A
2011-10-13 21:40             ` Martin Jansa [this message]
2011-10-13 22:16               ` Kamble, Nitin A
2011-10-04 11:03     ` Koen Kooi
2011-10-04 11:31       ` Martin Jansa
2011-09-30 17:16 ` [PATCH 0/4] Recipes upgrades Martin Jansa
2011-10-05  4:42 ` 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=20111013214048.GA3542@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=nitin.a.kamble@intel.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