Re: fixing libpthread noload, another approach

[manu%netbsd.org@localhost (Emmanuel Dreyfus)]

David Laight <david%l8s.co.uk@localhost> wrote:

> I presume that (effectively) forces RTLD_LAZY so you get the standard
> error when the PLT code fails to look up the sysmbol?

Yes, it does.
 
> That is just going to cause another splat of grief an a few months time.
> dlopen() failing probably gets logged sensibly.
> PLT functions failing to resolve names generates a horrid error exit.
> It will be even less obvious why things aren't working.

- programs linked without -lpthread that dlopen libpthread and then use
threads will fail, with an error as cryptic as it is now: without
appropriate logging, you do not know why it fails.

- programs linked without -lpthread that dlopen libpthread by do not use
threads will work as they did prior NetBSD 6.0. This is the benefit I am
looking for.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu%netbsd.org@localhost