Problems with f77 preproccesing under xlf (AIX)

[Chitov Iouri]

Dear gurus,

I found that  xlf fails to compile *.F files, which require preprocessing:

xlf -DPACKAGE_NAME=\"nemos\" -DPACKAGE_TARNAME=\"Strasbourg\ NEMOS\ 
simulation/analysis\" -DPACKAGE_VERSION=\"5.3\" -DPACKAGE_STRING=\"nemos\ 5.3\" 
-DPACKAGE_BU
GREPORT=\"address@hidden address@hidden" -DPACKAGE=\"nemos\" -DVERSION=\"5.3\" 
-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_UNISTD_H=1  -I. -I. 
-I/afs/in2p3.fr/cernlib/@sys/pro/includ
e -I/afs/in2p3.fr/cernlib/@sys/pro/include/cfortran    -g 
-WF,-D_LANGUAGE_FORTRAN -qextname                   -qmaxmem=8192 -check_bounds 
-c -o hrfile.o `test -
f 'hrfile.F' || echo './'`hrfile.F
xlf: 1501-210 command option P contains an incorrect subargument

xlf confuses with $(DEFS) statements included in PPF77COMPILE variable, as it 
treets -D options by their own special way.

The question how can I control separately compilation with preprocessing for cc 
and f77 compilers? E.g. don't send $(DEFS) for f77 compiler. From

my point of view it should be variable F77CPP to set F77 preprocessing options 
separately from C, as it organized now for C++ ($(CXXCPP) variable),

isn't it?

Please, send me answer by mail and thank you in advance

Yuriy.

--
 ---/---> Chitov Yuriy        The more, the better...