From owner-freebsd-hackers Thu May 23 07:56:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17928 for hackers-outgoing; Thu, 23 May 1996 07:56:53 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA17923 for ; Thu, 23 May 1996 07:56:50 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id IAA15769; Thu, 23 May 1996 08:55:18 -0600 Date: Thu, 23 May 1996 08:55:18 -0600 From: Nate Williams Message-Id: <199605231455.IAA15769@rocky.sri.MT.net> To: "Chris J. Layne" Cc: freebsd-hackers@freebsd.org Subject: Re: just a small observation In-Reply-To: References: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > /usr/bin/ld -e start -dc -dp -o foo /usr/lib/crt0.o /var/tmp/cc0013731.o > /usr/lib/libgcc.a -lc /usr/lib/libgcc.a .. > question, why does gcc cause ld to link in the libgcc library more than > once? Because there are dependencies that are necessary. > And is there any reason it isn't using the shared gcc library? Yes. Shared libraries should be for things that are *common* across OS's. Making *everything* a shared libraries means that anytime that library changes the user is forced to keep the old shlib around. For things like libgcc, anytime gcc is updated means the *entire* library is different. Making things like libc into shlibs is good, but the 'everything' is a shlib is a bad thing we've seen in the past. Having use 'real' shlibs for some time now, we have slowly moved back into what I would hope is an acceptable compromise between 'usefulness' and 'overboard'. Nate