* lconfig-native is not endian safe
@ 2011-03-30 14:47 Richard Purdie
2011-04-05 2:14 ` Khem Raj
0 siblings, 1 reply; 3+ messages in thread
From: Richard Purdie @ 2011-03-30 14:47 UTC (permalink / raw)
To: poky@yoctoproject.org, openembedded-core
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?
Cheers,
Richard
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: lconfig-native is not endian safe
2011-03-30 14:47 lconfig-native is not endian safe Richard Purdie
@ 2011-04-05 2:14 ` Khem Raj
2011-04-05 16:23 ` Richard Purdie
0 siblings, 1 reply; 3+ messages in thread
From: Khem Raj @ 2011-04-05 2:14 UTC (permalink / raw)
To: poky
On 3/30/2011 7: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.
>
FWIW it does not work with uclibc as well. So it should be disabled for
uclibc for all arches
> Short term we need to disable it at least for ppc, longer term what
> should we do?
>
> Cheers,
>
> Richard
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: lconfig-native is not endian safe
2011-04-05 2:14 ` Khem Raj
@ 2011-04-05 16:23 ` Richard Purdie
0 siblings, 0 replies; 3+ messages in thread
From: Richard Purdie @ 2011-04-05 16:23 UTC (permalink / raw)
To: Khem Raj; +Cc: poky
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-04-05 21:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-30 14:47 lconfig-native is not endian safe Richard Purdie
2011-04-05 2:14 ` Khem Raj
2011-04-05 16:23 ` Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox