Re: 20030411: Intel 7.1 compiler and netCDF

>To: address@hidden
>From: Tim Hoar <address@hidden>
>Subject: Re: 20030411: Intel 7.1 compiler and netCDF
>Organization: NCAR/CGD
>Keywords: 200304112246.h3BMkX7U003978 netCDF Intel 7.1 compilers

Tim,

> I think the install scripts need to be tweaked.
> I have had several bad experiences with "make install" completing normally
> but not working properly; mostly with the pieces pertaining to the f90
> interface.
> 
> The f90 example program
> (http://www.unidata.ucar.edu/packages/netcdf/f90/netcdf_test.f90)
> uses the typesizes module, so I got in the habit of using it.
> 
> Problem is, many installations don't get it "installed" by the
> 
> "configure", ...  "make install" procedure.
> 
> Building with the PG compiler results in a "typesizes.mod" file
> which is not installed to the same directory as "netcdf.mod".
> Note the base of the module name is not the same case as the source file
> root "typeSizes".
> 
> It is even worse with the Intel compiler,
> 
> -rw-rw-r--    1 8048     2000         2221 Apr  5  2000 netcdf.f90
> -rw-r--r--    1 root     root        83237 Apr 11 15:48 NETCDF.mod
> -rw-r--r--    1 root     root       422006 Apr 11 15:48 netcdf.o
> -rw-rw-r--    1 8048     2000         2551 Oct 24  2000 typeSizes.f90
> -rw-r--r--    1 root     root         1119 Apr 11 15:48 TYPESIZES.mod
> -rw-r--r--    1 root     root          829 Apr 11 15:48 typeSizes.o
> 
> and neither .mod file gets installed to the intended directory.
> 
> Maybe there needs to be a "make installcheck"  target?
> 
> Just thought you'd want to know -- Tim

Thanks for reporting the problem.  Unfortunately, there doesn't seem
to be a standard place to install Fortran 90 module files, nor a
standard for the case of module file names.  Currently our
f90/Makefile in the beta release is supposed to handle all the
variants

  netcdf.mod  NETCDF.mod  
  netcdf.MOD  NETCDF.MOD

and

  typesizes.mod  typeSizes.mod  TYPESIZES.mod  
  typesizes.MOD  typeSizes.MOD  TYPESIZES.MOD

and handle them the same way, so I don't understand why the module
files aren't geting installed in the include directory.  We'll have to
see if we can duplicate the problem here ...

--Russ