Re: bug? gemtext coompile error "po-lex.c:132: bad macro argument list"

[Bruno Haible]

Richard S. Blake writes:

> i've dl'd     the latest GETTEXT 
> (http://mirrors.kernel.org/gnu/gettext/gettext-0.11.1.tar.gz), and am 
> trying to install on MacOSX Server 10.1.3 (Darwin 5.3).
> 
> configure goes ok, but make results in:
> 
> 
> cc -DLOCALEDIR=\"/usr/local/share/locale\" 
> -DGETTEXTJAR=\"/usr/local/share/gettext/gettext.jar\" 
> -DLIBDIR=\"/usr/local/lib\" -DGETTEXTDATADIR=\"/usr/local/share/gettext\" 
> -DPROJECTSDIR=\"/usr/local/share/gettext/projects\" -DHAVE_CONFIG_H -I. -I. 
> -I.. -I. -I. -I.. -I../libuniname -I../lib -I../lib -I../intl -I../intl -g 
> -O2 -c po-lex.c  -fno-common -DPIC -o .libs/po-lex.lo
> po-lex.c:132: bad macro argument list
> po-lex.c:115: bad macro argument list
> po-lex.c:132: bad macro argument list
> po-lex.c:132: bad macro argument list
> cpp-precomp: warning: errors during smart preprocessing, retrying in basic 
> mode
> make[3]: *** [po-lex.lo] Error 1

Well, the line numbers refer to the include file po-lex.h, not
po-lex.c.

Probably a workaround is to use "cc -traditional-cpp" instead of "cc".

But in order to fix the gettext source, can you please tell me the
result of preprocessing the tiny file

=================== foo.c ========================
__GNUC__
__APPLE_CC__
__GNUC_MINOR__
==================================================

using "cc -E foo.c" ?

Bruno