From owner-freebsd-questions@FreeBSD.ORG Mon Dec 4 15:22:35 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 50F6F16A50A for ; Mon, 4 Dec 2006 15:22:35 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [63.240.77.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AF2543D1D for ; Mon, 4 Dec 2006 15:20:49 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from gimpy (c-24-118-173-219.hsd1.mn.comcast.net[24.118.173.219]) by comcast.net (sccrmhc14) with ESMTP id <20061204152119014006e0lee>; Mon, 4 Dec 2006 15:21:19 +0000 From: Josh Paetzel To: freebsd-questions@freebsd.org Date: Mon, 4 Dec 2006 09:20:56 -0600 User-Agent: KMail/1.9.4 References: <20061204130549.29737.qmail@web57807.mail.re3.yahoo.com> In-Reply-To: <20061204130549.29737.qmail@web57807.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612040920.56455.josh@tcbug.org> Cc: Rachel Florentine Subject: Re: Corrupted C Compiler X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 15:22:35 -0000 On Monday 04 December 2006 07:05, Rachel Florentine wrote: > 106Hi; > I entered the following stupid command: > cp -R /* /ad2 > thinking that would copy the contents of my working HD to my new > 1/2 teraflop HD (ad2). What it did was manage to wipe out some very > important files (thank goodness I had up-to-date backups) and it > appears to have corrupted gcc...my C compiler. I deduce this > because when I go to build Zope (as an example) from source I have > to run a script afterwards that repairs the broken C files. (This, > strangely, is not the case if I build Zope from port.) So, my > questions for you programmers more experienced than I, are: > > 1) Does my assessment make sense? Is gcc corrupt? > 2) Whether it is or not, how should I troubleshoot/fix my problem? > It seems to me I should re-install FBSD, but how? > > TIA, > Rachel > It's not immediately clear to me what you mean by repairing broken C files. The port uses the Zope source and the system compiler, presumably the same source and compiler you are using to build it by hand. Are you sure you aren't just 'doing it wrong' ? If you really suspect gcc is corrupted then some sort of binary repair is really your only option. A make buildworld/make installworld is unlikely to be feasible. -- Thanks, Josh Paetzel