From owner-freebsd-current Fri Mar 10 11:18:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22403 for current-outgoing; Fri, 10 Mar 1995 11:18:28 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA22397 for ; Fri, 10 Mar 1995 11:18:26 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA04485; Fri, 10 Mar 1995 11:18:12 -0800 From: Poul-Henning Kamp Message-Id: <199503101918.LAA04485@ref.tfs.com> Subject: Re: HEADS UP - About removing libgcc.so.261 To: davidg@Root.COM Date: Fri, 10 Mar 1995 11:18:11 -0800 (PST) Cc: wollman@halloran-eldar.lcs.mit.edu, freebsd-current@FreeBSD.org In-Reply-To: <199503101915.LAA07097@corbin.Root.COM> from "David Greenman" at Mar 10, 95 11:15:30 am Content-Type: text Content-Length: 1012 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... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'