From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: build breakage: python-native-2.6.1
Date: Sat, 14 Nov 2009 07:59:52 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911140758030.13079@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.0911140751320.12790@localhost>
On Sat, 14 Nov 2009, Robert P. J. Day wrote:
> On Sat, 14 Nov 2009, Philip Balister wrote:
>
> >
> >
> > On 11/13/2009 05:41 PM, Michael 'Mickey' Lauer wrote:
> > > Hi folks,
> > >
> > > > That readline tweak is a hack and there is a bigger problem here. I'd
> > > > like to solve it completely so yes, I'd like to confirm that was the
> > > > problem please. Once someone has done that I also have a proposed fix:
> > > >
> > > > http://tim.rpsys.net/python-hostfix.patch
> > >
> > > Acked-by: Michael 'Mickey' Lauer<mickey@vanille-media.de>
> >
> > Tested-by: Philip Balister <philip@balister.org>
> >
> > Fixed on F11.
> >
> > Philip
> >
> > PS: Yes, I know RP just pushed the patch.
>
> so there's only one package between me and a build of the
> beagleboard demo image -- guile-native -- and adrian alonso(?)
> allegedly posted a usable fix for that yesterday. looking good.
i just pulled that python patch and i'm still getting the same build
error as yesterday -- segmentation fault:
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: 12842 Segmentation fault (core dumped)
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
this is after "bitbake -c distclean python-native".
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-11-14 13:01 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
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 [this message]
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=alpine.LFD.2.00.0911140758030.13079@localhost \
--to=rpjday@crashcourse.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox