From owner-freebsd-current Wed Feb 14 23:32:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D9A0D37B4EC for ; Wed, 14 Feb 2001 23:32:34 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1F7WXW43163 for ; Thu, 15 Feb 2001 00:32:34 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102150732.f1F7WXW43163@harmony.village.org> To: freebsd-current@freebsd.org Subject: Re: Major bumping of libFOO In-reply-to: Your message of "Wed, 14 Feb 2001 23:25:03 PST." <20010214232503.A65907@dragon.nuxi.com> References: <20010214232503.A65907@dragon.nuxi.com> <200102142245.f1EMjvW67558@harmony.village.org> Date: Thu, 15 Feb 2001 00:32:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010214232503.A65907@dragon.nuxi.com> "David O'Brien" writes: : On Wed, Feb 14, 2001 at 03:45:57PM -0700, Warner Losh wrote: : > Here's a patch that I think will fix the major breakage with major : > library versions. : : I haven't tried to build -current for a few days now. Can you summerize : what breakage you are seeing? The problem is that new libFOO.so.N have references to __std{in,out,err}, instantly breaking all old binaries on the system. Eg, libcam.so.2 used to have __sF, which as defined in libc.so.[345]. However, after the bump to lib.so.5.XXXXXXX and rebuild the world, libcam.so.2 now references __std*. For apps that were linked before against libc.so.[345], this causes undefined symbols at runtime. Repeat for many other libraries than libcam. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message