From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26221 invoked by alias); 29 Oct 2012 14:30:05 -0000 Received: (qmail 25695 invoked by uid 48); 29 Oct 2012 14:29:45 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/55115] [>=4.5.0 regression] missing headers as fatal breaks cproto logic Date: Mon, 29 Oct 2012 14:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: preprocessor X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-10/txt/msg02681.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55115 --- Comment #2 from Jonathan Wakely 2012-10-29 14:29:44 UTC --- (In reply to comment #1) > If the headers do nothing, just delete them? If the headers do something, how > can you preprocess the file without the info from the headers? That won't work, I believe cproto parses the errors produced by GCC and figures out which declarations are missing based on the errors, then creates a header containing those declarations. Adding an option just for cproto is definitely not a good idea, just fix cproto instead. The right answer seems to be to create a directory of empty files with the names of the missing headers and point GCC to it with -I then cproto can proceed as normal, and generate replacements for the empty files. Refusing to compile when a header is missing is a huge improvement on the old behaviour.