From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: build breakage: python-native-2.6.1
Date: Fri, 13 Nov 2009 07:42:40 -0500 [thread overview]
Message-ID: <4AFD5440.6080202@balister.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911130732220.17745@localhost>
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
>
> rday
> --
>
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Twitter: http://twitter.com/rpjday
> ========================================================================
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2009-11-13 12:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 9:45 build breakage: python-native-2.6.1 Robert P. J. Day
2009-11-13 12:15 ` Philip Balister
2009-11-13 12:34 ` Robert P. J. Day
2009-11-13 12:42 ` Philip Balister [this message]
2009-11-13 13:19 ` Petr Štetiar
2009-11-13 15:41 ` Adrian Alonso
2009-11-13 16:16 ` Robert P. J. Day
2009-11-13 16:16 ` Richard Purdie
2009-11-13 16:29 ` Robert P. J. Day
2009-11-13 16:39 ` Richard Purdie
2009-11-13 17:13 ` Mike Westerhof
2009-11-13 22:41 ` Michael 'Mickey' Lauer
2009-11-14 12:50 ` Philip Balister
2009-11-14 12:52 ` Robert P. J. Day
2009-11-14 12:59 ` Philip Balister
2009-11-14 12:59 ` Robert P. J. Day
2009-11-14 13:13 ` Philip Balister
2009-11-14 13:17 ` Robert P. J. Day
2009-11-14 13:27 ` Robert P. J. Day
2009-11-14 14:23 ` Philip Balister
2009-11-14 13:15 ` Michael 'Mickey' Lauer
2009-11-13 16:42 ` Mike Westerhof
2009-11-13 17:26 ` Adrian Alonso
2009-11-13 17:50 ` Robert P. J. Day
2010-03-12 8:05 ` build breakage: python-native-2.6.4 (was build breakage: python-native-2.6.1) Steffen Sledz
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=4AFD5440.6080202@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.