public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug preprocessor/30808]  New: It would probably make sense to abort immediately after a file-not-found.
@ 2007-02-15 14:57 gcc-bugzilla at seebs dot net
  2007-02-15 17:51 ` [Bug preprocessor/30808] " pinskia at gcc dot gnu dot org
  0 siblings, 1 reply; 2+ messages in thread
From: gcc-bugzilla at seebs dot net @ 2007-02-15 14:57 UTC (permalink / raw)
  To: gcc-bugs

One of the most common problems I face in compiling programs with many
dependancies is that, if a dependency is missing, the resulting error messages
almost invariably scroll off the screen instantly, and even apart from the
scrolling, the single relevant error ("Cannot open <foo.h>: No such file or
directory" or whatever) is buried under hundreds upon hundreds of lines of
errors about variables not declared in scope, syntax errors in declarations,
and so on.

In general, error cascades are virtually impossible to prevent.

However, it seems clear that, any time an include file is missing, we *know*
that the build is doomed to failure.  I think it would be a nice option (and
possibly a very good default) for gcc to simply abort immediately after any
file-not-found message, on the grounds that, if you are missing a header file,
there is simply no point in telling you that, without that header, your program
doesn't work.


-- 
           Summary: It would probably make sense to abort immediately after
                    a file-not-found.
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: gcc-bugzilla at seebs dot net
 GCC build triplet: N/A
  GCC host triplet: N/A
GCC target triplet: N/A


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30808


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug preprocessor/30808] It would probably make sense to abort immediately after a file-not-found.
  2007-02-15 14:57 [Bug preprocessor/30808] New: It would probably make sense to abort immediately after a file-not-found gcc-bugzilla at seebs dot net
@ 2007-02-15 17:51 ` pinskia at gcc dot gnu dot org
  0 siblings, 0 replies; 2+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2007-02-15 17:51 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from pinskia at gcc dot gnu dot org  2007-02-15 17:51 -------


*** This bug has been marked as a duplicate of 15638 ***


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30808


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-02-15 17:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-15 14:57 [Bug preprocessor/30808] New: It would probably make sense to abort immediately after a file-not-found gcc-bugzilla at seebs dot net
2007-02-15 17:51 ` [Bug preprocessor/30808] " pinskia at gcc dot gnu dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).