Package: rats Severity: normal Tags: patch When building 'rats' on amd64 with gcc-4.0, I get the following error:
gcc -Wall -g -g -O2 -I/usr/local/include -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DYYTEXT_POINTER=1 -DHAVE_LIBEXPAT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_EXPAT_H=1 -DDATADIR=\"/usr/share/rats\" -o lex.yyc.o -c lex.yyc.c c-lex.l: In function 'yyclex': c-lex.l:67: error: invalid storage class for function 'preprocessor' c-lex.l: In function 'cstyle_comment': c-lex.l:314: warning: pointer targets in passing argument 1 of 'accumulate_comment' differ in signedness make[1]: *** [lex.yyc.o] Error 1 make[1]: Leaving directory `/rats-2.1' make: *** [build-stamp] Error 2 With the attached patch 'rats' can be compiled on amd64 using gcc-4.0. Regards Andreas Jochens diff -urN ../tmp-orig/rats-2.1/c-lex.l ./c-lex.l --- ../tmp-orig/rats-2.1/c-lex.l 2005-03-25 21:01:27.084545177 +0100 +++ ./c-lex.l 2005-03-25 21:01:07.415233072 +0100 @@ -31,7 +31,7 @@ static int identifier(void); static int string_const(void); -static int preprocessor(void); +int preprocessor(void); static void reset_comment(void); static int cstyle_comment(void); static void no_match(void); @@ -62,7 +62,7 @@ %} %% -%{static +%{ int preprocessor(void) { signed char c; diff -urN ../tmp-orig/rats-2.1/lex.yyc.c ./lex.yyc.c --- ../tmp-orig/rats-2.1/lex.yyc.c 2005-03-25 21:01:27.092543677 +0100 +++ ./lex.yyc.c 2005-03-25 21:01:25.262886728 +0100 @@ -5145,7 +5145,7 @@ static int identifier(void); static int string_const(void); -static int preprocessor(void); +int preprocessor(void); static void reset_comment(void); static int cstyle_comment(void); static void no_match(void); @@ -5310,7 +5310,7 @@ #line 64 "c-lex.l" -static + int preprocessor(void) { signed char c; -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]