parallel netcd 1.0.1 make errors on Apple

[William Gropp]

Fortran has two nearly incompatible formats for programs: the old  
(pre Fortran 90) format, called "fixed", and the newer "free"  
format.  If you cause the Fortran compiler to accept "free" format,  
it won't recognize "C" for comments.  The fix is relatively easy: for  
modern Fortran compilers, change all "C"s in column one into an  
exclamation point.  This works with most Fortran compilers in either  
format.

My guess in this case is that /usr/local/xlf/bin/mpif77 compiler is  
expecting free format, possibly because of a configuration setting or  
environment variable.

Bill

On Jan 10, 2007, at 2:51 PM, Robert Latham wrote:

> On Wed, Jan 10, 2007 at 11:27:14AM -0700, Amjad Majid Ali wrote:
>> Hi
>>
>> I am trying to compile parallel netcdf on Apple( darwin 8.8.0)
>>
>> I  am using ibm xlf  8.1 compiler.
>>
>> I am using  lam mpi
>>
>> i am attaching my config.log file
>>
>> This is error i am getting when i run make or gnumake
>>
>>
>> Making `all' in directory /Users/amjad/parallel-netcdf-1.0.1/src
>>
>> cd lib && make
>> ar cru libpnetcdf.a mpinetcdf.o header.o mpincio.o attr.o dim.o
>> error.o nc.o ncx.o string.o var.o ncmpidtype.o
>> ranlib libpnetcdf.a
>> if [ yes = yes ] ; then cd libf && make ; fi
>> /usr/local/xlf/bin/mpif77 -c -O3 strerrorf.f
>> "strerrorf.f", line 4.7: 1515-019 (S) Syntax is incorrect.
>> "strerrorf.f", line 5.7: 1515-019 (S) Syntax is incorrect.
>> ** nfmpi_strerror   === End of Compilation 1 ===
>> 1501-511  Compilation failed for file strerrorf.f.
>> make[3]: *** [strerrorf.o] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [subdir_target] Error 1
>> make: *** [src/lib/all] Error 2
>
> Huh... it would appear that your /usr/local/xlf/bin/mpif77 does not
> like it when .f files use C for comments.   We use C for comments all
> over the place, so I'm not sure what's wrong here.   We also use the
> xlf compiler (version 10) on our BlueGene and have reports of xlf
> working ok on some IBM SP machines, so I'm not entirely sure what
> is different about your situation and why we don't handle it.
>
>> Any solutions??
>
> Well, one solution would be to remove the comments from
> src/libf/strerrorf.f and also src/libf/inq_libversf.f and see how far
> you get.  Is there a compiler option for xlf to handle different
> comment styles?
>
> ==rob
>
> -- 
> Rob Latham
> Mathematics and Computer Science Division    A215 0178 EA2D B059 8CDF
> Argonne National Lab, IL USA                 B29D F333 664A 4280 315B
>