From owner-freebsd-current Thu Jan 13 11:56:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 3060914D7E; Thu, 13 Jan 2000 11:56:43 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA04218; Thu, 13 Jan 2000 20:33:40 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01564; Thu, 13 Jan 2000 20:35:16 +0100 (CET) (envelope-from wilko) Date: Thu, 13 Jan 2000 20:35:16 +0100 From: Wilko Bulte To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000113203515.A1321@yedi.iaf.nl> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> <20000113001631.C4148@yedi.iaf.nl> <20000112172522.A21639@dragon.nuxi.com> <20000113083024.A50096@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000113083024.A50096@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Jan 13, 2000 at 08:30:24AM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 08:30:24AM +0100, Wilko Bulte wrote: > On Wed, Jan 12, 2000 at 05:25:22PM -0800, David O'Brien wrote: > > On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote: > > > I copied libc.so.4 manually to /usr/lib but that is not sufficient. > > > It looks like ld-elf sticks to libc.so.4 even if I move the symlink > > > libc.so back from libc.so.4 to libc.so.3 > > > > Yes. Each shared library knows it's name when it was compiled (minor > > hand waving here). The linker then burns the shlib name (not file name, > > but shlib name gotten from a header in the shlib. > > The linker burns the shlib name into the executable it links, right? > Then why don't my executables linked end of december with libc.so.3 > work anymore? > > Essentially everything linked shared is now broken. And I have only > built/installed libc.so.4 (I did not get any further :/) and not any > executables. > > So, why are the 'old' executablas no longer working happily with libc.so.3 > they are linked to? Thanks to Marcel for flipping my misconception: I was under impression that libc.so.4 was a *new* libc.so, in other words that my freshly generated .4 was the first .4 ever. That was wrong, there has been a .4 before so the December executables also had internal references to the .4 version. I resurrected things by grabbing an 'old' .4 library from another Alpha. Now things work again. Wilko -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message