From owner-freebsd-current Thu May 14 02:39:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19174 for freebsd-current-outgoing; Thu, 14 May 1998 02:39:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19168 for ; Thu, 14 May 1998 02:39:27 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA03775; Thu, 14 May 1998 02:38:44 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: John Birrell cc: tlambert@primenet.com (Terry Lambert), current@FreeBSD.ORG Subject: Re: Undefined symbol "___error" In-reply-to: Your message of "Thu, 14 May 1998 13:24:38 +1000." <199805140324.NAA22813@cimlogic.com.au> Date: Thu, 14 May 1998 02:38:44 -0700 Message-ID: <3771.895138724@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bruce wants the change backed out. I haven't heard from anyone else. > Should I bump the major number of all the shared libraries in the > FreeBSD tree? Should I back out the change and forget about making future > objects thread-aware? Should I do nothing? Forward progress, especially in -current, has bumps. The shared libraries for 2.2.x will be provided as part of a "compat22" distribution for those who wish to support older shared executables so I'd say you should simply make sure that this works by bumping the numbers of any libs which are directly affected. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message