--p6hDAtPN9q+ZnUca
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 04, 2004 at 10:40:38PM +1100, matthew green wrote:
  |    How about we do this:
  |        *	use absolute symlinks for the runtime libraries
  |        	libfoo.so.M and libfoo.so.M.N.
  |        *	use relative symlinks for the link-time library libfoo.so.
  |    ?
  |   =20
  |    This would result in:
  |    	usr/lib/libz.so		-> ../../lib/libz.so
  |    	usr/lib/libz.so.0	-> /lib/libz.so.0
  |    	usr/lib/libz.so.0.3	-> /lib/libz.so.0.3
  |=20
  |=20
  | good idea.
  |=20
  |=20
  | i'm not sure that the usr/lib/lib/libfoo.so.M.N is actually necessary
  | even?  ld.so will load .so.M which has always been a symlink to the
  | real thing, and here it doesn't point to the symlink of the real thing,
  | but the real thing... i don't think usr/lib/libfoo.so.M.N links to
  | /lib are required in any case..?

The /usr/lib/libfoo.so.N.M symlinks to /lib were just for consistency
with the non-symlinked libraries.

I'm ambivalent about whether they're needed or not; I'll wait
to see what other toolchain-clued people have to say.

--p6hDAtPN9q+ZnUca
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAINsjpBhtmn8zJHIRAvurAJwLVz5skdJ6Upa0MXG7VM1sq7uhrgCfVkNT
nIQ5ODYz8X2P6xt8TBoB2xs=
=elqi
-----END PGP SIGNATURE-----

--p6hDAtPN9q+ZnUca--