Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: build breakage: python-native-2.6.4 (was build breakage: python-native-2.6.1)
Date: Fri, 12 Mar 2010 09:05:02 +0100	[thread overview]
Message-ID: <4B99F5AE.8010307@dresearch.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0911130443520.1157@localhost>

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.

The problem is back with python-native-2.6.4 and openSUSE 11.2. :(

It was solved for python-native-2.6.1 by this patch:

commit a4bddfe9e6a513a8ad1881ed2ffd419390cf20e7
Author: Richard Purdie <rpurdie <at> linux.intel.com>
Date:   Sat Nov 14 13:25:03 2009 +0100

    python-native: do not look in host paths for shared objects

Needs this patch to be adapted for all other python-native versions?

Steffen

-- 
Steffen Sledz
DResearch Digital Media Systems GmbH
Otto-Schmirgal-Str.3, D-10319 Berlin, Germany
Tel: +49 (30) 515932237 mailto:sledz@DResearch.DE
Fax: +49 (30) 515932299 http://www.DResearch.DE
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 54412;
Ust.-IDNr. DE169013825; WEEE Reg.-Nr. DE 85995642




      parent reply	other threads:[~2010-03-12  8:08 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
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 ` Steffen Sledz [this message]

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=4B99F5AE.8010307@dresearch.de \
    --to=sledz@dresearch.de \
    --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