From owner-freebsd-stable  Mon Jun 28 21:40: 9 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1220314D67; Mon, 28 Jun 1999 21:40:07 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA09337;
	Mon, 28 Jun 1999 21:39:30 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: John Birrell <jb@cimlogic.com.au>
Cc: stable@freebsd.org, jb@freebsd.org, eischen@vigrid.com
Subject: Re: pthreads in -stable 
In-reply-to: Your message of "Tue, 29 Jun 1999 14:22:37 +1000."
             <199906290422.OAA11718@cimlogic.com.au> 
Date: Mon, 28 Jun 1999 21:39:28 -0700
Message-ID: <9333.930631168@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Just take the libc_r from your current system. The internals of the
> implementation are (supposed to be) opaque. Should be easy to try
> out if the application is dynamically linked. At worst it'll be a 
> relink if the application is statically linked.

Hmmm.  The internals may be opaque but you bumped the revision number
for *some* reason that involved changing the interface or there'd have
been no reason to bump the number, si senor? :-)

In any case, the test app they sent me was indeed linked dynamic and
so I did attempt to simply copy a new -current libc_r.so.4 to
libc_r.so.3 for the app to use, and doing so caused it to die with a
signal 11 rather than an infinite loop so I deemed it a probable
mismatch and moved on.  Whether that judgement was too hasty will, I
hope, be proven either way once I get this product building under
-current entirely.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message