Portland Group cpp fails sanity check

[Brad Larsen]

I have a project that has been mostly switched to use autotools.  Seems to  
work OK with the GNU compilers.  When attempting to build on a cluster we  
have using the Portland Group toolchain, configure bails out saying the  
preprocessor is no good.

Anyone have insight?  I've attached the relevant segment of config.log.

Thanks!
Brad Larsen


configure:4132: checking how to run the C preprocessor
configure:4250: result: /opt/pgi/linux86-64/7.1-1/bin/pgcpp
configure:4274: /opt/pgi/linux86-64/7.1-1/bin/pgcpp  conftest.c
"conftest.c", line 16: error: identifier "Syntax" is undefined
             Syntax error
             ^

At end of source: error: expected a ";"

2 errors detected in the compilation of "conftest.c".
configure:4280: $? = 2
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "openggcm"
| #define PACKAGE_TARNAME "openggcm"
| #define PACKAGE_VERSION "trunk"
| #define PACKAGE_STRING "openggcm trunk"
| #define PACKAGE_BUGREPORT "address@hidden"
| #define PACKAGE "openggcm"
| #define VERSION "trunk"
| /* end confdefs.h.  */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
|            Syntax error
configure:4274: /opt/pgi/linux86-64/7.1-1/bin/pgcpp  conftest.c
"conftest.c", line 16: error: identifier "Syntax" is undefined
             Syntax error
             ^

At end of source: error: expected a ";"

2 errors detected in the compilation of "conftest.c".
configure:4280: $? = 2
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "openggcm"
| #define PACKAGE_TARNAME "openggcm"
| #define PACKAGE_VERSION "trunk"
| #define PACKAGE_STRING "openggcm trunk"
| #define PACKAGE_BUGREPORT "address@hidden"
| #define PACKAGE "openggcm"
| #define VERSION "trunk"
| /* end confdefs.h.  */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
|            Syntax error
configure:4349: error: C preprocessor  
"/opt/pgi/linux86-64/7.1-1/bin/pgcpp" fails sanity check
See `config.log' for more details.