Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Long compiler error messages not readable in the Problems view.

This is a known CDT problem.  The error parser is very aggressive and
flags all sorts of "normal" build output as errors.  You can attach your
messages to the bug.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=75078

  Jeremiah Lott
  TimeSys Corporation

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Kim Lux
> Sent: Thursday, November 10, 2005 4:38 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Long compiler error messages not 
> readable in the Problems view.
> 
> 
> 
> Wait a minute !  I don't think those are really build errors that are
> showing up in the problems screen:
> 
> a) I do a make clean.  I do a build and get 10 build errors.  
> Can't read
> them too long.  I build again and it builds perfectly.  No errors.  I
> think there is a bug in the gcc error parser, claiming there 
> are errors,
> but there aren't.  That is why it isn't stopping.  gcc isn't emitting
> any errors. The target runs fine.  
> 
> b) I quit eclipse and open a console in ../workspace/binutils.  I do a
> make clean and make.  No errors.  The target runs fine. 
> 
> The reason it isn't stopping is because there aren't really 
> any errors.
> There is, however a bug in the gcc error parsing code.       
> 
> 
> 
> On Thu, 2005-11-10 at 14:29 -0700, Kim Lux wrote:
> > On Thu, 2005-11-10 at 15:43 -0500, Doug Schaefer wrote:
> > > Make sure your build command doesn't have the -k option 
> to make. Then
> > > it
> > > should stop at the first failed compile.
> > 
> > I searched all the files in the project (including configs and
> > makefiles) and nowhere do we have a -k for a build flag.  I 
> am wondering
> > if it is in the code that builds the make string somewhere inside
> > Eclipse. 
> > 
> > So... man make gives:  
> > 
> > -S Cancel the effect of the -k option. This is never 
> necessary except in
> > a recursive make where -k might be inherited from the 
> top-level make via
> > MAKEFLAGS or if you set -k in MAKEFLAGS in your environment
> > 
> > So, in eclipse, Project->Properties-> "C/C++ Make Project"
> > 
> > I manually set the make command to be "make -S" and I 
> checked off "Stop
> > on first build error".  Actually, you can't check that off, 
> but I had it
> > checked off when I was using the default make command and 
> when I entered
> > my manual make command it stayed checked off even though 
> the text dims. 
> > 
> > My build still doesn't stop.
> > 
> > Me suspects there is a bug associated with that check off box.
> > 
> > Shall I enter a bug report or grab code and check it out 
> for myself ?
> > 
> > In order to use eclipse I have to be able to see the build errors in
> > order to be able to fix them.  
> > 
> -- 
> 
> Kim Lux,  Diesel Research Inc.
> 
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 


Back to the top