[uClibc] Re: The naming wars continue...
Peter S. Mazinger
ps.m at gmx.net
Tue Oct 26 12:32:36 UTC 2004
> On Tue Oct 26, 2004 at 11:19:30AM +0300, Denis Vlasenko wrote:
> > But how would it play together with glibc's /etc/ld.so.conf?
> > There may be a need to have them separated...
>
> There is an option to use a separate name...
>
> > I am asking this because I am in a midst of attempt
> > to make it possible to run binaries compiled for uclibc
> > on "normal" (glibc) system.
> >
> > 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.
>
> Well, they won't peacefully coexist in the same directory, thats
> for sure. The simplest method would be to use static linking.
> The next easiest way, would be to use current CVS uClibc, enable
> LDSO_CACHE_SUPPORT, change LDSO_BASE_FILENAME to something like
> "ld-uClibc.so", then setup /etc/ld-uClibc.so.conf with whatever
> directories you want to use for uClibc linked shared libs and run
> ldconfig to create /etc/ld-uClibc.so.cache.
>
> > (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)
They can coexist for runtime usage definitely if:
1. enable cache and change the LDSO_BASE_FILENAME, as mentioned above
2. if you use the uClibc ld.so (ld-uClibc.so.0), not the system-provided
version
3. if you append some suffix to the libpthread.so.0 (if you need it), this
one conflicts w/ the glibc one
4. Take care, that all of the used additional libs (ex. zlib) are in a
path defined in the newly prefixed LDSO_BASE_FILENAME, but are not
present in some common path (/lib;/usr/lib), the glibc version of
these libs are also not allowed to be present in the common path.
If this approach is to difficult, build against these statically.
I am using it as described above, the development is done in chroot (and
packaged).
I won't even try to mix the development environments.
Peter
--
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
More information about the uClibc
mailing list