Re: default linker for shared libraries, need some comments

[Andreas Jaeger <aj at suse dot de>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 25 April 2003 15:21, Yaroslav Popovitch wrote:
> On Fri, 25 Apr 2003, Andreas Jaeger wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Thursday 24 April 2003 22:31, Yaroslav Popovitch wrote:
> > > Hi! I had some problems with setting default linker for shared
> > > libraries. They are always linked against ld-linux.so.2. Option
> > > --dynamic-linker works only for usual programs.
> >
> > Why are you trying to do this?  It sounds like a real hack.  You always
> > need to link against the same dynamic linker as the C library comes from.
> >  So, even if you would succeed, you might have a dynamic linker that does
> > not work with the C library that you have and your program will break
> > badly.
>
> This is related to lsb runtime implementation. At this moment
> /lib/ld-lsb.so.1 is a link to /lib/ld-linux.so.2. I found that
> applications compiled with patched gcc are linked against
> /lib/ld-lsb.so.1. But shared libraries are still linked against
> ld-linux.so.2. I was trying to solve this problem.

You need a proper lsb build environment including a glibc that is linked 
against ld-lsb.so.1 and that exports symbols in a way that linking against 
that library will produce an LSB compliant application.  There's a sample LSB 
implementation that should do this, look at it,

Andreas
- -- 
 Andreas Jaeger
  SuSE Labs aj at suse dot de
   private aj at arthur dot inka dot de
    http://www.suse.de/~aj
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE+qUbnOJpWPMJyoSYRAjviAJ9FFv4ti17QK9nnAzMOvGVXQu8kqQCfVPaa
qnrTZNVPvg1Fslhf2kvtJDg=
=szmz
-----END PGP SIGNATURE-----