From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: prelink issue with ppc64?
Date: Wed, 3 Aug 2011 09:37:20 -0500 [thread overview]
Message-ID: <4E395D20.8020608@windriver.com> (raw)
In-Reply-To: <BC707063-0722-4F72-A066-4E811125354B@kernel.crashing.org>
On 8/3/11 12:35 AM, Kumar Gala wrote:
> If prelink gets a chance to properly run I get a rootfs that does:
>
> /sbin/init: relocation error: /lib64/libc.so.6: symbol _rtld_global_ro, version GLIBC_PRIVATE not defined in file ld64.so.1 with link time reference
>
> if 'baselib' is set to /lib we get:
>
> /local/home/galak/git/poky/build-p5020/tmp/sysroots/x86_64-linux/usr/sbin/prelink: /sbin/init.sysvinit: Using /lib/ld64.so.1, not /lib64/ld64.so.1 as dynamic linker
>
> if 'baselib' is set to /lib64 we get:
>
> Assigned virtual address space slots for libraries:
> /lib64/ld64.so.1 00000080f4910000-00000080f49473d0
> /lib64/libc.so.6 00000080f4950000-00000080f4afe090
> /lib64/libdl.so.2 00000080f4b10000-00000080f4b23520
> /lib64/libcrypt.so.1 00000080f4b10000-00000080f4b57708
> /lib64/libutil.so.1 00000080f4b10000-00000080f4b234a0
> Would prelink /lib64/ld-2.13.so
> Would prelink /lib64/libc-2.13.so
>
> Not sure what prelink is doing but it seems to breaking things. Any ideas?
>
> ---
>
> I'm also concerned that we use /etc/prelink.conf when invoking prelink.
Prelinker is being run within the rootfs, so the /etc/prelink.conf being used is
the one inside of the image -- NOT the system version.
I would suspect that the cross-prelinker rtld emulation is likely setup for the
LSB style library paths and may be causing some of the problems.
I'd suggest simply disabling prelink and getting everything to work first.. once
it does we can work through any prelinker issues. (Prelink on PPC64 hasn't been
tested within the oe-core environment.. so it could very well have issues beyond
the ld.so path.)
--Mark
> - k
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-08-03 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 5:35 prelink issue with ppc64? Kumar Gala
2011-08-03 14:37 ` Mark Hatle [this message]
2011-08-03 14:53 ` Kumar Gala
2011-08-03 15:09 ` Mark Hatle
2011-08-04 5:37 ` Kumar Gala
2011-08-04 14:03 ` Kumar Gala
2011-08-04 15:12 ` Mark Hatle
2011-08-04 15:05 ` Mark Hatle
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=4E395D20.8020608@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@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