From owner-freebsd-current@FreeBSD.ORG Mon Jul 26 21:03:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A98916A4CE for ; Mon, 26 Jul 2004 21:03:09 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4072843D53 for ; Mon, 26 Jul 2004 21:03:09 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i6QL30Uj058231; Mon, 26 Jul 2004 14:03:04 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200407262103.i6QL30Uj058231@gw.catspoiler.org> Date: Mon, 26 Jul 2004 14:03:00 -0700 (PDT) From: Don Lewis To: dwhite@gumbysoft.com In-Reply-To: <20040726130939.J32820@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-current@FreeBSD.org Subject: Re: syntax errors in standard headers!? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 21:03:09 -0000 On 26 Jul, Doug White wrote: > On Sat, 24 Jul 2004, Evan Dower wrote: > >> WIth the instability issues of late, I recently had a crash in the middle of >> portupgrading. This left many packages with no +CONTENTS file. Thus I >> figured I would simply reinstall them. Unfortunately when I try to reinstall >> any of them I tend to get errors such as: >> /usr/include/stdlib.h:46: error: syntax error before "typedef" >> and >> /usr/include/locale.h:42: error: syntax error before "struct" >> >> I get all kinds of other errors too. Basically not a whole lot is working >> properly, even though I have updated -CURRENT since the crash. Most recently >> on Thursday. > > Some port's .h file probably got corrupted and its leaving things in an > insconsistent state when the system headers come along. Inspect a file > that doesn't compile and trace the included files to find the corrupted > one. gcc's -E option comes in very handy for debugging problems like this. Direct the package build output to a file. Go to the directory that the compiler was running in when it croaked. Execute the compiler command that croaked, with the addition of the -E option, and the removal of the -o outputfile option. You'll probably want to redirect the output to a file. The -C and -dD options may also be helpful.