From owner-freebsd-questions Tue Feb 17 15:40:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22283 for freebsd-questions-outgoing; Tue, 17 Feb 1998 15:40:18 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from proxyb2.san.rr.com (proxyb2-atm.san.rr.com [204.210.0.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22112 for ; Tue, 17 Feb 1998 15:39:30 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (dt050ndd.san.rr.com [204.210.31.221]) by proxyb2.san.rr.com (8.8.7/8.8.8) with ESMTP id PAA27940; Tue, 17 Feb 1998 15:38:07 -0800 (PST) Message-ID: <34EA1F5F.FBF8F285@san.rr.com> Date: Tue, 17 Feb 1998 15:38:07 -0800 From: Studded Organization: Triborough Bridge and Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE-0216 i386) MIME-Version: 1.0 To: Doug White CC: freebsd-questions@FreeBSD.ORG Subject: Re: gcc 2.8.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > > On Mon, 16 Feb 1998, Studded wrote: > > > > gcc requries massive hacking to work. Check in on the -hackers mail > > > archives for current progess; we're still working on it. > > > > This is a question I've been meaning to ask. I always took not being > > able to upgrade gcc in stride because it's not been a priority for me. > > However I was looking over some security stuff and one of the first > > recommendations for securing a high priority machine is to remove the > > compiler. I know that gcc is tightly integrated into FreeBSD, but I'm > > wondering now if that's such a good idea. > > Blowing it away is OK. I did it pretty quickly on a 40MB printserver I > put together last week. > > rm /usr/bin/gcc /usr/bin/cc /usr/libexec/cc1plus .... > rm -rf /usr/include Ok, that helps. > This was while sysinstall was still downloading stuff :-) Of course I did > the bonehead thing of removing /usr/lib; luckily mount_nfs is statically > linked! Hehehe.. I know that feeling. > > Which leads me to my question. Are there any plans to dis-integrate gcc > > from the base? It seems like the gcc folks are being more agressive > > about more frequent upgrades, so it would be nice to be able to play > > around with them. > > The main problem upgrading gcc is that FSF doesn't recognize a.out and we > haven't converted to ELF yet. Secondly, the FreeBSD project prefers to > wait it out until gcc falls into a proven stable release. The early > several releases are often buggy and patches quickly follow. Why do you > think we run 2.7.2.1 and not 2.7.0? ;-) Ahhhh.. Ok. I guess I misunderstood the integration problems. Thanks for clearing it up for me. Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message