"error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token" compiler error

[chales]

Hi,

another newby trip-up I expect....

When I build the project (yes I have done 'build all')

../src/ivk_scaler.c:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token

../src/ivk_scaler.c:172: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token

../src/ivk_scaler.c:223: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token

../src/ivk_scaler.c:269: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token

../src/ivk_scaler.c:402: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token

../src/ivk_scaler.c:433: error: old-style parameter declarations in prototyped function definition

../src/ivk_scaler.c:433: error: expected '{' at end of input

make: *** [src/ivk_scaler.o] Error 1

inside the .c file the function syntx looks fine.

paths look OK.

This is the only error. It looks like a missing brace, but I can't see it.

No joy from other posts on this issue.

Do I have a switch wrong in a .h someplace? Any clues?

A bit lost.

cheers

colin

[gszakacs]

This would be pretty hard to debug without looking at the source code.  One thing

that can cause problems like this is an errant macro definition.  For example having

an unintended semicolon at the end of a definition like:

#define FOO  5 ;

Since the macro pre-processor will insert the semicolon as well as the 5 when the

macro is used, you can have any number of syntax errors.  Is there something common

to all of the lines where you get the error?

-- Gabor

[gszakacs]

One more thing, if you have any #include files in the offending source, the extra or

mising brace could be in the include file rather than the source where the errors occur...

[chales]

Problem solved... there was some kind of invisible corruption in the .c

Igot another copy (looked the same) from a colleague's machine ... worked fine.

Hate it when that happens.

Thanks

Colin

[Shynutpirate]

Hey..could u please share me the detailed report on how you rectified the error.