[uClibc] Re: The naming wars continue...

Joakim Tjernlund joakim.tjernlund at lumentis.se
Thu Oct 28 11:07:20 UTC 2004


> On Tuesday 26 October 2004 11:55, Ivan Popov wrote:
> > On Tue, Oct 26, 2004 at 11:19:30AM +0300, Denis Vlasenko wrote:
> > > So far, I am wrestling with stuffing all uclibc libs
> > > into separate [/usr]/libu, because I see no way
> > > for uclibc-compiled glib to peacefully coexist with
> > > glibc-compiled one.
> > > 
> > > (The immediate goal is to have uclibc Midnight Commander to
> > > run on glibc system without breaking stuff. That's why I need
> > > both glibc- and uclibc-compiled glib)
> > 
> > Hello,
> > 
> > using this occation for a reminder - as soon as uclibc would get
> > an explicit runtime loader, like glibc has,
> > it will be possible to seamlessly run an application,
> > with an arbitrary collection of libraries, without collisions,
> > via a simple wrapper.
> > You could do things which you can't with LD_LIBRARY_PATH.
> > 
> > Please consider the useful design features...
> 
> For the record: this would (and it did for me) break horribly
> with uc-programs exec-ing glibc ones.
> 
> uc-Midnight Commander was working okay but couldn't run even a
> /bin/sh.
> 
> I ended up patching ld-uClibc-0.9.26.so:

[SNIP]

You could make "/lib:/usr/lib" a config option to uClibc. Glibc has
something similar, SYSTEM_DIRS if I recall correctly. 
Then you could also control the usage of "/usr/X11R6/lib" in uClibc.

 Jocke




More information about the uClibc mailing list