From owner-freebsd-questions Mon Feb 16 22:51:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13084 for freebsd-questions-outgoing; Mon, 16 Feb 1998 22:51:09 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13067 for ; Mon, 16 Feb 1998 22:51:06 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id WAA11341; Mon, 16 Feb 1998 22:50:53 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 16 Feb 1998 22:50:53 -0800 (PST) From: Doug White Reply-To: Doug White To: Studded cc: freebsd-questions@FreeBSD.ORG Subject: Re: gcc 2.8.0 In-Reply-To: <34E922A8.77A3F96A@san.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 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! > 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? ;-) > More importantly it would be nice to be able to trim > gcc out with one fell swoop when needed. Obviously this would be a > -current thing, but I'm wondering if its on the drawing board. removing gcc is simply removing the headers and binaries and some of the libs. You can probably figure out what you need and what you don't. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message