From owner-freebsd-current Fri Mar 10 18:55:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02327 for current-outgoing; Fri, 10 Mar 1995 18:55:29 -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 SAA02311 for ; Fri, 10 Mar 1995 18:55:24 -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 SAA03775; Fri, 10 Mar 1995 18:55:09 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id SAA00129; Fri, 10 Mar 1995 18:55:09 -0800 Message-Id: <199503110255.SAA00129@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Bruce Evans cc: freebsd-current@FreeBSD.org Subject: Re: HEADS UP - About removing libgcc.so.261 In-reply-to: Your message of "Sat, 11 Mar 95 12:04:04 +1000." <199503110204.MAA15780@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 10 Mar 1995 18:55:06 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >>>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. > >The same fix is probably required for other previously-shared libraries >such as libcompat. > >I'm still concerned about the static libgcc unnecessarily bloating all >executables by 4K, partly because the of linkage order bugs. It doesn't bloat anything I tried by 4k...very little if anything seems to be included from it. -DG