[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020228: netCDF Fortran-90 on UXP/V: typeSizes unavailable

Frank,

Sorry for taking so long to reply.  Our Fortran-90 expert was on
vacation.

> From: Frank Schmitz <address@hidden>
> Organization: ?
> Keywords: 200202220850.g1M8oax11501 netCDF F90

The above message contained the following:

> Hello,
> we have some problems to compile the fortran source. What's going wrong?
> Best Regards,
> Frank
> 
> Please send e-mail back to address@hidden
> 
> UNIX_System_V hikvpp-00 4.1 ES 3 5000 UXP/V
> /home/vpp5000/hik/schmitz/WORK/a/netcdf-3.5.0/src
> frt is /usr/lang/bin/frt
> cc is a tracked alias for /usr/lang/bin/cc
> CC is /usr/lang/bin/CC
> 
> 
> 
> creating cache ./config.cache
> checking for top-level source-directory
> /work4/hik/schmitz/a/netcdf-3.5.0/src
> checking for m4 preprocessor
> checking for m4... m4
> checking m4 flags... -B10000
> checking C compiler "cc"... works
> checking how to make dependencies... false
> checking for CC... CC
> checking C++ compiler "CC"... works
> checking how to run the C preprocessor... cc -E
> checking user-defined Fortran-77 compiler "frt"... works
> checking for Fortran .F compiler... 
> checking if Fortran-77 compiler handles *.F files... yes
> checking "frt" as Fortran-90 compiler... works
> checking for nm utility
> checking for nm... nm
> checking nm flags... 
> checking for C-equivalent to Fortran routine "SUB"... sub_
> checking for Fortran "byte"... yes
> checking for Fortran "integer*2"... yes
> checking if Fortran "byte" is C "signed char"... yes
> checking if Fortran "byte" is C "short"... no
> checking if Fortran "byte" is C "int"... no
> checking if Fortran "byte" is C "long"... no
> checking if Fortran "integer*2" is C "short"... yes
> checking if Fortran "integer*2" is C "int"... no
> checking if Fortran "integer*2" is C "long"... no
> checking if Fortran "integer" is C "int"... yes
> checking if Fortran "real" is C "float"... yes
> checking if Fortran "doubleprecision" is C "double"... yes
> checking for Fortran-equivalent to netCDF "byte"... byte
> checking for Fortran-equivalent to netCDF "short"... integer*2
> checking for math library
> checking for tanh in -lc... no
> checking for tanh in -lm... yes
> checking for ar utility
> checking for ar... ar
> checking ar flags... cru
> checking for nm utility
> checking for nm... (cached) nm
> checking nm flags... 
> checking for ranlib... :
> checking for stdlib.h... yes
> checking for sys/types.h... yes
> checking for strerror... yes
> checking for working ftruncate()... yes
> checking for working alloca.h... yes
> checking for alloca... yes
> checking for st_blksize in struct stat... yes
> checking for IEEE floating point format... yes
> checking for ANSI C header files... yes
> checking for size_t... yes
> checking for off_t... yes
> checking for ssize_t... yes
> checking for ptrdiff_t... yes
> checking for uchar... no
> checking whether char is unsigned... no
> checking whether byte ordering is bigendian... yes
> checking size of short... 2
> checking size of int... 4
> checking size of long... 8
> checking size of float... 4
> checking size of double... 8
> checking size of off_t... 8
> checking size of size_t... 8
> checking for catman... no
> checking for makewhatis... no
> checking for /usr/lib/makewhatis... no
> checking for manual-page index command... 
> checking binary distribution directory... /home/ftp/pub/binary/dummy_system
> updating cache ./config.cache
> creating ./config.status
> creating macros.make
> udcreating fortran/nfconfig.inc
> creating libsrc/ncconfig.h
> 
> 
> Making `all' in directory /work4/hik/schmitz/a/netcdf-3.5.0/src/libsrc
> 
>       cc -c -O -I.  -DNDEBUG attr.c
>       cc -c -O -I.  -DNDEBUG dim.c
>       cc -c -O -I.  -DNDEBUG error.c
>       cc -c -O -I.  -DNDEBUG -DVERSION=`cat ../VERSION` libvers.c
>       cc -c -O -I.  -DNDEBUG nc.c
>       cc -c -O -I.  -DNDEBUG ncio.c
>       cc -c -O -I.  -DNDEBUG ncx.c
>       cc -c -O -I.  -DNDEBUG putget.c
>       cc -c -O -I.  -DNDEBUG string.c
>       cc -c -O -I.  -DNDEBUG v1hpg.c
>       cc -c -O -I.  -DNDEBUG v2i.c
>       cc -c -O -I.  -DNDEBUG var.c
>       ar cru libnetcdf.a attr.o  dim.o  error.o  libvers.o  nc.o  ncio.o  
> ncx.o  putget.o  string.o  v1hpg.o  v2i.o  var.o
>       : libnetcdf.a
> 
> Returning to directory /work4/hik/schmitz/a/netcdf-3.5.0/src
> 
> 
> Making `all' in directory /work4/hik/schmitz/a/netcdf-3.5.0/src/fortran
> 
>       cc -c -O -I../libsrc  -DNDEBUG fort-attio.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-control.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-dim.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-genatt.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-geninq.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-genvar.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-lib.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-misc.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-v2compat.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-vario.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-var1io.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-varaio.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-varmio.c
>       cc -c -O -I../libsrc  -DNDEBUG fort-varsio.c
>       ar cru ../libsrc/libnetcdf.a fort-attio.o        fort-control.o  
> fort-dim.o      fort-genatt.o   fort-geninq.o   fort-genvar.o   fort-lib.o    
>   fort-misc.o     fort-v2compat.o         fort-vario.o    fort-var1io.o   
> fort-varaio.o   fort-varmio.o   fort-varsio.o
>       : ../libsrc/libnetcdf.a
> 
> Returning to directory /work4/hik/schmitz/a/netcdf-3.5.0/src
> 
> 
> Making `all' in directory /work4/hik/schmitz/a/netcdf-3.5.0/src/f90
> 
>       frt -c  typeSizes.f90
>       frt -c  netcdf.f90
>  UXP/V  Fortran V20L20  Fri Feb 22 09:31:05 2002
> 
>  Diagnostic messages: program name(netcdf)
>  Module subprogram name(nf90_put_var_OneByteInt)
>   jwd2018i-s   "netcdf_expanded.f90", line 3: When IMPLICIT NONE is 
> specified, values must be declared in a type declaration statement.
>   jwd1185i-s   "netcdf_expanded.f90", line 5: In an initialization or 
> specification expression, OneByteInt must be a named constant.
>   jwd1326i-s   "netcdf_expanded.f90", line 5: Type specification or length 
> specification invalid.
>   jwd2006i-i   "netcdf_expanded.f90", line 10: counter is declared but never 
> referenced.
>  Module subprogram name(nf90_put_var_TwoByteInt)
>   jwd2018i-s   "netcdf_expanded.f90", line 20: When IMPLICIT NONE is 
> specified, values must be declared in a type declaration statement.
>   jwd1185i-s   "netcdf_expanded.f90", line 22: In an initialization or 
> specification expression, TwoByteInt must be a named constant.
>   jwd1326i-s   "netcdf_expanded.f90", line 22: Type specification or length 
> specification invalid.
>   jwd2006i-i   "netcdf_expanded.f90", line 27: counter is declared but never 
> referenced.
>  Module subprogram name(nf90_get_var_text)
>   jwd2006i-i   "netcdf_text_variables.f90", line 27: textDimIDs is declared 
> but never referenced.
>   jwd2006i-i   "netcdf_text_variables.f90", line 27: localIndex is declared 
> but never referenced.
>   jwd2006i-i   "netcdf_text_variables.f90", line 29: stringLength is declared 
> but never referenced.
>   jwd2006i-i   "netcdf_text_variables.f90", line 29: counter is declared but 
> never referenced.
>   jwd1370i-s   "netcdf.f90", line 37: Module typeSizes is not available.
...

The above is consistent with the Fortran-90 compiler not having
the definitions from the file "typeSizes.f90" available when it
compiles the file "netcdf.f90". I note that the compilation command for
"typeSizes.f90" doesn't have the "frt" banner following it that the
compilation command for "netcdf.f90" does. I further note that the last
line above indicates that the "typeSizes" module was unavailable. Could
it be that the file "typeSizes.f90" was never actually compiled? Does
the file "typeSizes.o" exist? Is it valid?

Regards,
Steve Emmerson   <http://www.unidata.ucar.edu>