From owner-freebsd-current Fri Mar 10 18:42:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA01901 for current-outgoing; Fri, 10 Mar 1995 18:42:24 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA01894 for ; Fri, 10 Mar 1995 18:42:21 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id SAA03032; Fri, 10 Mar 1995 18:41:40 -0800 From: "Rodney W. Grimes" Message-Id: <199503110241.SAA03032@gndrsh.aac.dev.com> Subject: Re: HEADS UP - About removing libgcc.so.261 To: bde@zeta.org.au (Bruce Evans) Date: Fri, 10 Mar 1995 18:41:39 -0800 (PST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199503110204.MAA15780@godzilla.zeta.org.au> from "Bruce Evans" at Mar 11, 95 12:04:04 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1107 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. Is what really scares me is one could rewrite most of /bin /sbin /usr/bin /usr/sbin in perl and decrease the size of the installed system while not slowing it down any :-(. While almost all of the binaries are 4K larger than 1.1.5, many of them are 8K larger :-(. And some of them have grown by leaps and bounds. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD