From owner-freebsd-current Thu Oct 14 14:45:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CC95414BDC for ; Thu, 14 Oct 1999 14:45:09 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA17233; Thu, 14 Oct 1999 14:45:08 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA07475; Thu, 14 Oct 1999 14:45:07 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910142135.RAA00099@pcnet1.pcnet.com> Date: Thu, 14 Oct 1999 14:45:07 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Daniel Eischen Subject: Re: World breakage in libc_r? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > John Polstra 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? Oh, maybe, but be careful. Weak symbols don't solve very many kinds of problems, but they can sure cause a lot of trouble. I don't have time to work through this case in detail right now. But think about whether a call to read() from inside libc will get the correct version in all cases. Consider both static and dynamic linking too -- they don't behave quite the same. There are lots of potential gotchas. Sorry to be so brief. I can help more with this after FreeBSDCon. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message