From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: glibc_2.9.bb do_package failed
Date: Tue, 1 Jun 2010 14:48:20 +0200 [thread overview]
Message-ID: <20100601124820.GD5446@jama> (raw)
In-Reply-To: <1275395992.6382.176.camel@mill.internal.reciva.com>
On Tue, Jun 01, 2010 at 01:39:52PM +0100, Phil Blundell wrote:
> On Tue, 2010-06-01 at 14:33 +0200, Martin Jansa wrote:
> > On Tue, Jun 01, 2010 at 05:35:03PM +0530, Soumya R wrote:
> > > qemu-arm: relocation error: qemu-arm: symbol fcntl, version GLIBC_2.0 not defined in file libpthread.so.0 with link time reference
> > > NOTE: Task failed: localedef returned an error (command was PATH="/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/armv5te-angstrom-linux-gnueabi:/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/armv5te-angstrom-linux-gnueabi:/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/sbin:/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin:/home/likewise-open/KPIT/soumyar/oe/build/tmp/cross/armv5te//bin:/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/sbin:/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/bin:/likewise-open/KPIT/soumyar/oe/bitbake/bin:/likewise-open/KPIT/soumyar/oe/bitbake/bin:/likewise-open/KPIT/soumyar/oe/bitbake/bin:/home/likewise-open/KPIT/soumyar/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" I18NPATH="/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/armv5te-angstrom-linux-gnueabi/glibc-2.9-r36.3/locale-t
> ree/
> > > usr/share/i18n" qemu-arm -s 1048576 -r 2.6.24 -L /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/armv5te-angstrom-linux-gnueabi/glibc-2.9-r36.3/locale-tree -E LD_LIBRARY_PATH=/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/armv5te-angstrom-linux-gnueabi/glibc-2.9-r36.3/locale-tree/lib /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/armv5te-angstrom-linux-gnueabi/glibc-2.9-r36.3/locale-tree/bin/localedef --force --old-style --no-archive --prefix=/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/armv5te-angstrom-linux-gnueabi/glibc-2.9-r36.3/locale-tree --inputfile=/usr/share/i18n/locales/es_NI --charmap=UTF-8 es_NI).
> >
> > Are you using latest qemu-native from OE? Otherwise you still need 0 in mmap_min_addr.
> >
> > Try to run that command by hand in console to see if it's the same issue.
>
> This doesn't look like an mmap_min_addr kind of problem. It seems like
> there is some mismatch between the version of libpthread that qemu was
> compiled against and the one that it is running against. The only
> obvious cause that springs to mind would be if you were sharing the
> build tree between multiple hosts, and the host where qemu was compiled
> is not the same as the one where it's trying to run.
Ah, you're right, I apologize. I overlooked first line about fcntl.
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2010-06-01 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <76E258664B189C4CBEF125491CA11ECC9445E0CF7C@KCINPUNHJCMS01.kpit.com>
2010-06-01 12:05 ` glibc_2.9.bb do_package failed Soumya R
2010-06-01 12:33 ` Martin Jansa
2010-06-01 12:39 ` Phil Blundell
2010-06-01 12:48 ` Martin Jansa [this message]
2010-06-02 9:07 Soumya R
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=20100601124820.GD5446@jama \
--to=martin.jansa@gmail.com \
--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