On Thu, Oct 14, 1999 at 05:35:05PM -0400, Daniel Eischen wrote:
> One of the things on my wish list is a libpthread that can be linked
> with libc. So the way to accomplish this is to have null hooks with
> weak symbols in libc, and provide the same (non-null) functions in
> libpthread but with strong symbols?
Weak symbols don't work too well _between_ libraries. If libc is linked
before libpthread, any unresolved references when libc is searched will
use the weak symbols from there, regardless of the fact that a strong
symbol exists in libpthread. If libc is linked after libpthread, then
you can have libc internal references to things that should been resolved
to things in libpthread, but end up using the weak symbols in libc
because that is all there is left. 8-(
Not a simple problem to solve. The current tools don't help at all. A
second library pass to resolve weak symbols would have been better. It's
too late for that now, though, since you can change the semantics on the
shared loader.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
