From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre Haupt <andre@bitwigglers.org>
Cc: yocto@yoctoproject.org
Subject: Re: Bitbaking python fails
Date: Fri, 22 Jul 2011 10:48:52 +0100 [thread overview]
Message-ID: <1311328132.2344.106.camel@rex> (raw)
In-Reply-To: <20110722093722.GA8668@localhost.localdomain>
On Fri, 2011-07-22 at 11:37 +0200, Andre Haupt wrote:
> Hi Richard,
>
> thanks for your answer. See below ...
>
> On Fri, Jul 22, 2011 at 09:59:51AM +0100, Richard Purdie wrote:
> > On Fri, 2011-07-22 at 10:37 +0200, Andre Haupt wrote:
> > > Hi all,
> > >
> > > Building python for poky bernard fails for me with the following error:
> > >
> > > ...
> > > ...
> > > Looking in tk80 for ['/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib']
> > > Looking in tcl80 for ['/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib']
> > > *** WARNING: renaming "gdbm" since importing it failed: libgdbm.so.3:
> > > cannot open shared object file: No such file or directory
> > > /bin/sh: line 1: 12830 Illegal instruction (core dumped)
> > > LD_LIBRARY_PATH=/home/ahaupt/yocto-git/build/tmp/work/core2-poky-
> > > linux/python-2.6.6-nk1.2/Python-2.6.6:/home/ahaupt/yocto-git/build
> > > /tmp/sysroots/i686-linux/usr/bin/../lib/pseudo/lib:/home/ahaupt
> > > /yocto-git/build/tmp/sysroots/i686-linux/usr/bin/../lib/pseudo/lib64
> > > CC='ccache i586-poky-linux-gcc -m32 -march=core2 -msse3
> > > -mtune=generic -mfpmath=sse
> > > --sysroot=/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc'
> > > LDSHARED='ccache i586-poky-linux-gcc -m32 -march=core2 -msse3
> > > -mtune=generic -mfpmath=sse
> > > --sysroot=/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc
> > > -shared' LDFLAGS='-Wl,-O1 -Wl,--as-needed'
> > > OPT='-fexpensive-optimizations -fomit-frame-pointer
> > > -frename-registers -O2 -ggdb -feliminate-unused-debug-types'
> > > /home/ahaupt/yocto-git/build/tmp/sysroots/i686-linux/usr/bin/python
> > > -E ./setup.py -q build
> > > make: *** [sharedmods] Error 132
> > > FATAL: oe_runmake failed
> > > ERROR: Function 'do_compile' failed (see
> > > /home/ahaupt/yocto-git/build/tmp/work/core2-poky-linux/
> > > python-2.6.6-nk1.2/temp/log.do_compile.12751
> > > for further information)
> > >
> > > Does this sound familiar to anyone? libgdbm.so.3 exists in
> > > /home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib and points to
> > > libgdbm.so.3.0.0
> > >
> > > My target machine is atom-pc and my build host is Fedora 13 in a
> > > VirtualBox machine.
> >
> > I've not seen this before. You could run
> > "file /home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib/libgdbm.so.3.0.0" and check that its of the correct architecture since the invalid instruction is a weird error to see. I'm not 100% sure its that file its complaining about the instruction from though.
>
> this is the output of the file command:
> libgdbm.so.3.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1
> (SYSV), dynamically linked, not stripped
Sounds correct...
> > Does it do this every build, erroring in the same way? I know we did see
> > some emulation corruption type issues with virtualbox in the past
> > although they've not been reported for a while. It might be worth
> > starting a new build of "bitbake python" and see if the error is
> > reproducible too...
>
> It happens reproducible when i do a "bitbake python".
Is this on a fresh clean build directory?
You could also try "bitbake -c cleansstate python gdbm" on your existing
build directory and retry "bitbake python" to see if its reproducible
that way.
Cheers,
Richard
next prev parent reply other threads:[~2011-07-22 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 8:37 Bitbaking python fails Andre Haupt
2011-07-22 8:59 ` Richard Purdie
2011-07-22 9:37 ` Andre Haupt
2011-07-22 9:48 ` Richard Purdie [this message]
2011-07-22 12:32 ` Andre Haupt
2011-11-13 1:05 ` João Henrique Freitas
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=1311328132.2344.106.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=andre@bitwigglers.org \
--cc=yocto@yoctoproject.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.