--ibq+fG+Ci5ONsaof
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 05, 2007 at 02:46:39AM +0100, Lubomir Sedlacik wrote:
> On Sun, Mar 04, 2007 at 06:47:58PM +0000, David Laight wrote:
> > I think that it may only be necessary to create a small .so containing
> > the new syscall stubs.  Then only the new libpthread would be needed.
> >=20
> > Maybe ld.so.conf could get the library loaded, alternatively it could
> > be built with a .SONAME matching that of libpthread, with a .NEEDED
> > entry to pull in the new libpthread itself.
>=20
> both ways work, i just tested.  here's what i did.

Yes, but it was very much expected.  The question is:  what's easier?
libc, libcrypt and libpthread are part of a normal build, as we do every
week, so distribution is not a problem.  I don't see how we would build
that small .so, except as a one time thing and provide just the binary
on the site.  Less than ideal.

[...]
> but these work only for the load time.  how would you solve the issue at
> the link time?

What kind of issue could there possibly be at link (ld, not ld.so_elf)
time?

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.

--ibq+fG+Ci5ONsaof
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iQEVAwUBRevGzdgoQloHrPnoAQIqqwgAkg5MKZ4VvEVVWRTgg2srboOMRGx+r0/4
cQJ4mBC/4v6G6VBKhEedw/VGVEkmCEd828sJFvpAlDKlwpyu7K3M5naWuya0tbeU
9SrHOj6wCIMjscZuMli5pO4uqfLJFf62Wq7UPfUeOENYwQ43nBLK5VMsgYM5aLH7
fKS9l7tgOvDO3KujKHMBcrIRhcfRob0FURVOnWf/X8018TSwNVlryLWct/ZJz5/5
1VDH879bHU7LxxH1X+USMNFDg9Kzn3KYb+2jYGVJrF3eOi7aL60geMjsvAFykQSk
Yap+/burfyDIMXRiLtzJ7CeDeAxrkgWv6StkH69FB17B2Kn1D4rA+w==
=V2FJ
-----END PGP SIGNATURE-----

--ibq+fG+Ci5ONsaof--