Why lib/interp.c?

[Joakim Tjernlund]

> -----Original Message-----
> From: uclibc-bounces at uclibc.org 
> [mailto:uclibc-bounces at uclibc.org] On Behalf Of Rob Landley
> Sent: den 8 januari 2007 00:43
> To: uClibc
> Subject: Why lib/interp.c?
> 
> This overrides the shared libraries' path to the shared 
> library loader.  
> Question: why do blah.so files even _have_ a path to the 
> shared library 
> loader?

I remember playing with this long time ago and from what little I
can recall is that I don't think they have to be here, but removing
it broke some tool, possibly one of the utils.

> Don't you already need a shared library loader 
> running in order to 
> be able to load the suckers in the first place?  Why can't 
> that one work 
> recursively?
> 
> I'm confused.  Each executable can only have one shared 
> library loader, even 
> when it links against a dozen shared libraries.  So all the 
> libraries an 
> executable links directly against have to be able to be 
> loaded by the same 
> shared library loader.  Why should the libraries it links 
> _indirectly_ 
> against be any different?
> 
> What's the point here?