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 theProblems view. 
Hi All, 
	
	I have been following this thread. My 2 cents are as follows :

	(a) [Conflicting Path]
		We can avoid this by asking the gcc to send the full path
whenever an option like FULL_PATH is set before running the gcc. If the full
path of a file is emitted, then the Conflicting path can be immediately
removed.

	(b) For error messages that are appearing in more than one line. 
		We can redirect the make output as follows which will make
the error messages to appear in one single line. 
		command.add( "2>&1 | /bin/cat 1>&2" );
		


Thanks,
Bala  

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Ploett, Norbert
Sent: Friday, November 11, 2005 12:37 PM
To: CDT General developers list.
Subject: AW: [cdt-dev] Long compiler error messages not readable in
theProblems view.

Hi Kim (and Joanne),

actually I would say that 84647 is a duplicate of
https://bugs.eclipse.org/bugs/show_bug.cgi?id=108920, which is fixed and the
fix should be available in CDT 3.0.1

Cheers,


Norbert

-----Ursprüngliche Nachricht-----
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Kim Lux
Gesendet: Donnerstag, 10. November 2005 23:09
An: CDT General developers list.
Betreff: RE: [cdt-dev] Long compiler error messages not readable in the
Problems view.

I think this bug is at the root of the problem. 84647

I think I have to turn off the error parser for now.  


On Thu, 2005-11-10 at 16:40 -0500, Doug Schaefer wrote:
> In that case, a bug report would be fine. If you can capture the build 
> output and attach it to the bug report, that would help us as well.
> 
> Thanks,
> Doug
> 
> > -----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 Pr oblems 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
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
--
Kim Lux,  Diesel Research Inc.


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top