Date: Thu, 13 Jan 2000 08:30:24 +0100 From: Wilko Bulte <wilko@yedi.iaf.nl> To: "David O'Brien" <obrien@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000113083024.A50096@yedi.iaf.nl> In-Reply-To: <20000112172522.A21639@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Jan 12, 2000 at 05:25:22PM -0800 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Wilko ('puzzled') -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000113083024.A50096>