Completion 2.0M7 w/ 3.0M6 on RH9 [message #96597] |
Sun, 14 March 2004 03:13  |
Eclipse User |
|
|
|
Hi Guys,
I am not able to get code completion to work at all, not even using the
printf example from the FAQ. As gcc is very popular, I must be doing
something wrong. I have set the correct paths in the project properties.
The CDT .log reports:
MESSAGE Scanner Exception: IProblem : Expression Evaluation error for
condition
: !defined __GNUC__ || __GNUC__ < 2 in file: /usr/include/sys/cdefs.h on
line: 166
So its finding it, but what happens next I don't understand. Any pointers
appreciated -- I hope my mistake is not too obvious. There seem to be alot
of Expression Evaluation errors associated with macro definitions.
Matt
PS
Thanks for the tool. Keep up the good work.
|
|
|
|
Re: Completion 2.0M7 w/ 3.0M6 on RH9 [message #96628 is a reply to message #96613] |
Sun, 14 March 2004 17:55  |
Eclipse User |
|
|
|
Thanks for the help. I made sure that I again tried several variations.
Bug 54778 has been submitted!
David Daoust wrote:
> I think that you will need to define __GNUC__ to either 2 (for gcc version
> 2) or 3 (for gcc version 3).
> I would guess that the short circuit evaluation of the expression is broken.
> ( if the first part of the expression is true, then we should not evaluate
> the || part).
> If this "fixes" your problem, please raise a bugzilla report on it.
> - Dave
> "Matt" <dmatt001@yahoo.com> wrote in message
> news:c3146t$h45$1@eclipse.org...
> > Hi Guys,
> >
> > I am not able to get code completion to work at all, not even using the
> > printf example from the FAQ. As gcc is very popular, I must be doing
> > something wrong. I have set the correct paths in the project properties.
> >
> > The CDT .log reports:
> >
> > MESSAGE Scanner Exception: IProblem : Expression Evaluation error for
> > condition
> > : !defined __GNUC__ || __GNUC__ < 2 in file: /usr/include/sys/cdefs.h on
> > line: 166
> >
> > So its finding it, but what happens next I don't understand. Any pointers
> > appreciated -- I hope my mistake is not too obvious. There seem to be alot
> > of Expression Evaluation errors associated with macro definitions.
> >
> > Matt
> >
> > PS
> > Thanks for the tool. Keep up the good work.
> >
|
|
|
Powered by
FUDForum. Page generated in 0.06007 seconds