From owner-freebsd-current  Sat Mar 15 02:30:02 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA15088
          for current-outgoing; Sat, 15 Mar 1997 02:30:02 -0800 (PST)
Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA15055
          for <current@FreeBSD.org>; Sat, 15 Mar 1997 02:29:55 -0800 (PST)
Received: (from helbig@localhost)
	by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id LAA01247;
	Sat, 15 Mar 1997 11:29:43 +0100 (MET)
From: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De>
Message-Id: <199703151029.LAA01247@helbig.informatik.ba-stuttgart.de>
Subject: Re: why /usr/libexec/cc* static?
In-Reply-To: <87n2s5msv9.fsf@plm.xs4all.nl> from Peter Mutsaers at "Mar 15, 97 10:01:14 am"
To: plm@xs4all.nl (Peter Mutsaers)
Date: Sat, 15 Mar 1997 11:29:43 +0100 (MET)
Cc: current@FreeBSD.org
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi Peter,

> Hello,
> 
> I just did a make world again, with current (without any problems for
> the first time since the Lite-2 merge started!).
> 
> I noted that /usr/libexec/cc* (the C compiler passes) are linked
> statically, and wonder why? cpp and cc itself are linked dynamically,
> so it's not as if one could recompile libc in case something would be
> wrong with libc.so etc.
> 

Here is the answer:

(cvs log Makefile ...)

RCS file: /usr/cvsroot/src/gnu/usr.bin/cc/cc1/Makefile,v
Working file: Makefile
[...]
head: 1.11
[...]
----------------------------
revision 1.7
date: 1995/10/01 20:16:27;  author: davidg;  state: Exp;  lines: +2 -1
Build cc1 nonshared. This actually results in it consuming 40K *less* disk
space and improves compile times by a few percent.
----------------------------

Wolfgang