From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: lconfig-native is not endian safe
Date: Tue, 05 Apr 2011 17:23:01 +0100 [thread overview]
Message-ID: <1302020581.24596.494.camel@rex> (raw)
In-Reply-To: <4D9A7AEC.9020206@gmail.com>
On Mon, 2011-04-04 at 19:14 -0700, Khem Raj wrote:
> On 3/30/2011 7:47 AM, Richard Purdie wrote:
> > 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.
> >
>
> FWIW it does not work with uclibc as well. So it should be disabled for
> uclibc for all arches
I've queued a patch to do this.
Cheers,
Richard
prev parent reply other threads:[~2011-04-05 21:25 UTC|newest]
Thread overview: 11+ 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
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
2011-04-05 2:14 ` Khem Raj
2011-04-05 16:23 ` Richard Purdie [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=1302020581.24596.494.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
/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.