From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: lconfig-native is not endian safe
Date: Wed, 30 Mar 2011 10:43:56 -0500 [thread overview]
Message-ID: <4D934FBC.40802@windriver.com> (raw)
In-Reply-To: <1301496447.24596.100.camel@rex>
On 3/30/11 9:47 AM, Richard Purdie wrote:
> Hi,
>
> Poky has had a ldconfig-native recipe in for a while. Back in the times
> our RPATHS were totally broken adding in an ld.so.cache was useful. In
> modern times I'm having trouble working out when this would be useful on
> a standard system as libraries are pretty much always in one of the two
> default search locations.
>
> ldconfig-native is 32/64 bit safe. I've just been looking at PPC and it
> is certainly not endian safe though. The endianess of the target system
> need to match that of the build system for it to work. It wouldn't be
> much work to make it endian safe though although the codebase will
> diverge further from that in (e)glibc though.
>
> Short term we need to disable it at least for ppc, longer term what
> should we do?
On ARM, are the structures packed in the same way as the target system?
I know I prefer to NOT use ldconfig in the systems I design, but I understand
why people want it.
I suggest we disable it on PPC for now, and work on updating endian support,
(packing if necessary) and make sure that it supports the latest ldconfig
features of being able to use referenced directories and such.
--Mark
> Cheers,
>
> Richard
>
>
> _______________________________________________
> 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-03-30 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 14:47 lconfig-native is not endian safe Richard Purdie
2011-03-30 15:43 ` Mark Hatle [this message]
2011-03-31 1:59 ` Kamble, Nitin A
2011-03-31 2:02 ` Kamble, Nitin A
2011-03-31 2:09 ` Kamble, Nitin A
2011-03-31 9:02 ` Hatle, Mark
2011-03-31 10:40 ` Richard Purdie
2011-03-31 17:27 ` ldconfig-native " Kamble, Nitin A
2011-04-05 2:15 ` lconfig-native " Khem Raj
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=4D934FBC.40802@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