From owner-freebsd-current Fri Mar 10 11:36:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22787 for current-outgoing; Fri, 10 Mar 1995 11:36:45 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA22781 for ; Fri, 10 Mar 1995 11:36:42 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA03228; Fri, 10 Mar 1995 11:36:28 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id LAA09487; Fri, 10 Mar 1995 11:36:27 -0800 Message-Id: <199503101936.LAA09487@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Poul-Henning Kamp cc: wollman@halloran-eldar.lcs.mit.edu, freebsd-current@FreeBSD.org Subject: Re: HEADS UP - About removing libgcc.so.261 In-reply-to: Your message of "Fri, 10 Mar 95 11:18:11 PST." <199503101918.LAA04485@ref.tfs.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 10 Mar 1995 11:36:26 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >> >>> I just ran into a major problem with removing the shared version of >> >>> gcc (libgcc.so.261.0), it seems that XFree86 3.1 is dynamically linked >> >>> against this. >> >> you shouldn't remove it until you are sure you don't need it... >> > >> >There is a more serious problem: unless GCC is modified, so long as >> >you have this shared library, `ld' will prefer it to the static >> >version, thus ensuring that future binaries require it. >> >> Poul modified ld to force it to build with the static version. I'm coming >> up right now with a better fix (to cc) that will tell the linker to use the >> static version of the library. >> >Actually, I guess I have found an even better solution: > > move ths shared libgcc to /usr/lib/FreeBSD-2.0-compat > tell ldconfig about that directory. > >ld should not find it, but ldconfig will... This will work (and we should do this), but people doing upgrades will still have the old libgcc.so. I'll be committing a (very) good fix for the problem shortly. -DG