This is the mail archive of the
mailing list for the glibc project.
Re: Prelinking of shared libraries
On Sat, May 05, 2001 at 10:41:33AM +0200, Jakub Jelinek wrote:
> On Sat, May 05, 2001 at 09:19:51AM +0200, Andreas Jaeger wrote:
> > Exactly. The idea is that the one configuration program (let's say
> > ldconfig) loads all libraries into its address space, prelinks them
> > and saves the prelinked files together with information where they
> > should be mmapped. The dynamic linker then reads this information and
> > tries to mmap the prelinked libs into the same address as the
> > configuration program. If the mmap fails, the lib will be loaded as
> > if it was not prelinked and relocated normally.
> Note that the one configuration program has to work on most of system
> binaries as well in addition to all libraries (well, again, does not have to
> be all, just the most widely used majority).
Why has the configuration program to work on system binaries?
I agree, we have to add some way to define which libraries will be
prelinked and this should be configurable.
SuSE Labs email@example.com