Post #3574317

if compilation fails somewhere in gcc's includes, usually there's an issue with your code. if compilation fails somewhere in gcc's includes in THIS mess, usually it ends up being a processor-specific nightmare. today's bug: `extern char *gettext(const char *);` from libintl is a syntax error near "const". no, no preceding lines have fucked up nesting or unterminated lines and there's no preprocessor statements directly before this line. it's just fucked, but ONLY on the original Pentium through the Pentium MMX. 486? Pentium 2 Xeon? Totally fine.