`fatal' mismatched in current tree

Robert Lipe robertlipe@usa.net
Sun Apr 18 09:38:00 GMT 1999

I've had variations of this for a few days now.   I suspect it's fallout
from the recent changes in internal error handling.

stage2/xgcc -Bstage2/ -B/usr/local/i686-pc-sco3.2v5.0.5/bin/ -c  -DIN_GCC     -W -Wall -O2 -g   -DHAVE_CONFIG_H    -I. -I../../egcs/gcc -I../../egcs/gcc/config -I../../egcs/gcc/../include ../../egcs/gcc/gen-protos.c
../../egcs/gcc/gen-protos.c: In function `fatal':
../../egcs/gcc/gen-protos.c:199: argument `s' doesn't match prototype
../../egcs/gcc/system.h:387: prototype declaration

In gen-protos.c, it's
	fatal (s)
	     char *s;

In system.h, it's
	extern void fatal PVPROTO((const char *, ...)) ATTRIBUTE_PRINTF_1 ATTRIBUTE_NORETURN;

I'm unsure which is on the way in and which is on the way out, so no patch...

More information about the Gcc-bugs mailing list