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: [review/test 3/5] python, python-native: upgrade from 2.6.6 to 2.7.2
Date: Sun, 23 Oct 2011 08:28:13 +0200	[thread overview]
Message-ID: <20111023062813.GC3497@jama.jama.net> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94E33A6D8D@orsmsx504.amr.corp.intel.com>

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

On Sat, Oct 22, 2011 at 04:54:00PM -0700, Kamble, Nitin A wrote:
> Hi Martin,
>   I have kept my python work at nitin/python branch on poky contrib. the 2.7.2 python is working for all arches except arm. And I am going on vacation for few days, and I could not finish the python arm issue arm, so if you get a chance you can look into the arm issue, if you have not resolved it already then I will look into it again once I am back from my vacation on 13th Nov.

Hi Nitin,

I've tried already and failed, but I'll try again and I guess qemux86-64
(linking to host libc and failing if it's not same version as the one in
sysroot) is also still broken and should be taken care of too, right?

Regards,

> > -----Original Message-----
> > From: openembedded-core-bounces@lists.openembedded.org
> > [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> > Martin Jansa
> > Sent: Friday, October 14, 2011 2:12 AM
> > To: Patches and discussions about the oe-core layer
> > Subject: Re: [OE-core] [review/test 3/5] python, python-native: upgrade
> > from 2.6.6 to 2.7.2
> > 
> > On Fri, Oct 14, 2011 at 10:19:39AM +0200, Martin Jansa wrote:
> > > On Thu, Oct 13, 2011 at 04:06:13PM -0700, nitin.a.kamble@intel.com
> > wrote:
> > > > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > >
> > >
> > > This patch does not apply after
> > > 9f9612d15acc6ee3b71f52bdb3f1ec4cb56b1a17
> > >
> > > can you rebase on top of oe-core?
> > >
> > > Also please drop
> > > DEFAULT_PREFERENCE = "-27"
> > >
> > > we have only one python version so I guess it's not usefull at all
> > > anymore
> > >
> > > I'll apply it manually, test it here.. and report if those modules
> > are
> > > build later..
> > 
> > seems the same as with previous version..
> > 
> > log.do_compile full of
> > /OE/shr-core/tmp/sysroots/x86_64-linux/usr/lib/libpython2.7.so: file
> > not recognized: File format not recognized
> > collect2: ld returned 1 exit status
> > 
> > and only built module is sqlite
> > OE @ ~/shr-core/tmp/work/armv4t-oe-linux-gnueabi/python-2.7.2-r0.0 $ ls
> > Python-2.7.2/build/lib.linux-x86_64-2.7/
> > _sqlite3.so
> > 
> > while with 2.6 we had a lot of modules
> > $ ls Python-2.6.6/build/lib.linux-x86_64-2.6/
> > _bisect.so          _codecs_jp.so    _ctypes.so        _fileio.so
> > _json.so             _random.so   _testcapi.so  bz2.so
> > datetime.so         itertools.so  parser.so    spwd.so
> > unicodedata.so
> > _bytesio.so         _codecs_kr.so    _ctypes_test.so   _functools.so
> > _locale.so           _socket.so   _weakref.so   cPickle.so    fcntl.so
> > math.so       pyexpat.so   strop.so    zlib.so
> > _codecs_cn.so       _codecs_tw.so    _curses.so        _hashlib.so
> > _lsprof.so           _sqlite3.so  array.so      cStringIO.so
> > future_builtins.so  mmap.so       readline.so  syslog.so
> > _codecs_hk.so       _collections.so  _curses_panel.so  _heapq.so
> > _multibytecodec.so   _ssl.so      audioop.so    cmath.so      gdbm.so
> > nis.so        resource.so  termios.so
> > _codecs_iso2022.so  _csv.so          _elementtree.so   _hotshot.so
> > _multiprocessing.so  _struct.so   binascii.so   crypt.so      grp.so
> > operator.so   select.so    time.so
> > 
> > Can you please test that you have non-empty python-syslog python-
> > resource python-elementtree python-fcntl python-zlib?
> > And test build for qemuarm, because I guess that it links to -native
> > libpython2.7 when you're building qemux86 on x86 host.
> > 
> > But it seems that python runtime works now, thanks!
> > 
> > Regards,
> > --
> > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

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

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

  reply	other threads:[~2011-10-23  6:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 23:06 [review/test 0/5] Python upgrade and other commits nitin.a.kamble
2011-10-13 23:06 ` [review/test 1/5] x86 tune files: set baselib for x32 tune as libx32 nitin.a.kamble
2011-10-13 23:06 ` [review/test 2/5] python-dbus: upgrade from 0.83.2 to 0.84.0 nitin.a.kamble
2011-10-13 23:06 ` [review/test 3/5] python, python-native: upgrade from 2.6.6 to 2.7.2 nitin.a.kamble
2011-10-14  8:19   ` Martin Jansa
2011-10-14  9:11     ` Martin Jansa
2011-10-14 12:03       ` Kamble, Nitin A
2011-10-22 23:54       ` Kamble, Nitin A
2011-10-23  6:28         ` Martin Jansa [this message]
2011-10-24  0:07           ` Kamble, Nitin A
2011-10-24  6:05             ` Martin Jansa
2011-10-29 20:21               ` Martin Jansa
2011-10-29 20:22                 ` [PATCH] python-2.7.2: fix build issues when additional modules are linked against host or native libpython instead of target Martin Jansa
2011-10-30  7:33                   ` [PATCHv2] " Martin Jansa
2011-10-23  6:53         ` [review/test 3/5] python, python-native: upgrade from 2.6.6 to 2.7.2 Koen Kooi
2011-10-15 13:05     ` Martin Jansa
2011-10-13 23:06 ` [review/test 4/5] python: update generate-manifest for 2.7 version and regenerate it nitin.a.kamble
2011-10-13 23:06 ` [review/test 5/5] update python 2.7 manifest nitin.a.kamble
2011-10-14  3:33 ` [review/test 0/5] Python upgrade and other commits Kamble, Nitin A

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=20111023062813.GC3497@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