This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Sharing ld.so.cache between two glibc versions on a single system
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Dmitry Mikushin <dmitry at kernelgen dot org>
- Cc: "Carlos O'Donell" <carlos at systemhalted dot org>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Sat, 09 Nov 2013 22:36:28 -0500
- Subject: Re: Sharing ld.so.cache between two glibc versions on a single system
- Authentication-results: sourceware.org; auth=none
- References: <527E481D dot 2010708 at kernelgen dot org> <CAE2sS1jFcZVMA5rJErdsbQQ4TUaNgS9R+iM80o-QPLvhLtYgjg at mail dot gmail dot com> <527E9D3C dot 5070203 at kernelgen dot org> <527EFAA6 dot 8090604 at redhat dot com> <527EFECA dot 8060807 at kernelgen dot org>
On 11/09/2013 10:34 PM, Dmitry Mikushin wrote:
> No, I do not expect "format guarantee", format obviously changes once
> in a while.
>
> The exact problem I'm trying to protect against is inability of
> alternative GLIBC to find shared libraries defined in system's
> /etc/ld.so.conf.d without user intervention.
>
> As one possible direction I see myself: are there any ways to turn our
> alternative GLIBC into "a client" of system's GLIBC cache lookup
> function? This way lookup function stays compatible with the format,
> while alternative GLIBC gets access to the cache.
>
> I really hope it's clear enough,
It's not clear at all yet. You still haven't described a problem.
With what prefix did you configure your glibc?
Cheers,
Carlos.