[oe] build breakage: python-native-2.6.1

[Richard Purdie]

On Fri, 2009-11-13 at 07:42 -0500, Philip Balister wrote:
> On 11/13/2009 07:34 AM, Robert P. J. Day wrote:
> > On Fri, 13 Nov 2009, Philip Balister wrote:
> >
> >> On 11/13/2009 04:45 AM, Robert P. J. Day wrote:
> >>>
> >>>     building beagleboard-demo-image:
> >>>
> >>> NOTE: make -j4 BUILD_SYS= HOST_SYS= LIBC=
> >>> STAGING_LIBDIR=/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/lib
> >>> STAGING_INCDIR=/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/include
> >>> *** WARNING: renaming "dbm" since importing it failed:
> >>> build/lib.linux-x86_64-2.6/dbm.so: undefined symbol: dbm_firstkey
> >>> /bin/sh: line 1:   515 Segmentation fault
> >>> LD_LIBRARY_PATH=/home/rpjday/oe/angstrom-dev/work/x86_64-linux/python-native-2.6.1-ml8.2/Python-2.6.1:
> >>> CC='ccache gcc -pthread' LDSHARED='ccache gcc -pthread -shared'
> >>> OPT='-DNDEBUG -g  -O3 -Wall -Wstrict-prototypes' ./python -E ./setup.py -q
> >>> build
> >>> make: *** [sharedmods] Error 139
> >>> FATAL: oe_runmake failed
> >>>
> >>>     that's it, that's the entire log file.  and it's entirely
> >>> reproducible.
> >>
> >> Well, your and my setups are the same :) Graeme is the the other F11 user and
> >> it is working for him :(
> >
> >    i'm not on F11 anymore, i'm effectively on F12 (fully-updated f12
> > beta).  i made the upgrade a couple days ago and that's when those
> > other packages broke.  hmmmm ... i really should have made that
> > chronological connection.
> >
> >    but after the upgrade, i did a full rebuild of everything and those
> > were the only packages to fail.  so, percentage-wise, that's not bad.
> 
> I'm on F11 fwiw.
> 
> I got this from gsb and a core file:
> 
> http://pastebin.ca/1669812
> 
> Philip

Can someone with this problem please run a python-native build with
http://tim.rpsys.net/python-debug.patch applied?

There should be some debug at the end of the do_compile log afterwards.
I see:

Looking in ncursesw for ['/media/build1/builds/oe/angstrom/tmp/staging/x86_64-linux/usr/lib', '/usr/local/lib', '.', '/lib64', '/usr/lib64', '/lib', '/usr/lib']
Looking in ncurses for ['/media/build1/builds/oe/angstrom/tmp/staging/x86_64-linux/usr/lib', '/usr/local/lib', '.', '/lib64', '/usr/lib64', '/lib', '/usr/lib']
Found /media/build1/builds/oe/angstrom/tmp/staging/x86_64-linux/usr/lib/libncurses.so

and I'm guessing it finds ncursesw in /lib/lib64 for some people.

I also see some other worrying entries on my system :(

Cheers,

Richard