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

20010124: typesizes.f90 - should it be part of libnetcdf.a?

Mary,

Yes.  The file "typeSizes.o" should be in the library "libnetcdf.a".
Your makefile "f90/Makefile" has a bug in it that causes this object
file to *not* be added to the library.  The makefile will be fixed in
the next release.

I suggest modifying the makefile -- adding the string "typeSizes.o" to
the LIB_OBJS macro -- then executing a "make" in the "f90/"
subdirectory.  You should see the module being added to the netCDF
library.

Please let me know if this helps.

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

> From: Mary Haley <address@hidden>
> Subject: typesizes.f90 - should it be part of libnetcdf.a?
> Organization: NCAR/SCD
> Keywords: 200101241712.f0OHCeX14218 netCDF F90 typesizes
>
> I've been building netcdf-3.5-beta6 for Phil Rasch who wants to use
> the f90 interface.  I'm not at all familiar with this interface, but
> Phil was having trouble with it on an AIX system because of an
> undefined reference:
> 
>   ld: 0711-317 ERROR: Undefined symbol: .__typesizes_MOD__&&_typesizes
> 
> He noticed that this symbol is defined in the netcdf-3.5-beta/src/f90
> directory in typeSizes.f90.  Should typeSizes.o be getting compiled
> into libnetcdf.a? It doesn't currently appear to be the case. There are
> some other files in this directory that I'm also wondering if they
> should be getting built into libnetcdf.a.
> 
> The documentation at:
> 
> http://www.unidata.ucar.edu/packages/netcdf/f90/Documentation/f90-html-docs/guide25.html#1018063
> 
> didn't mention anything about these files, so I'm not sure how to
> proceed.
> 
> Thanks,
> 
> --Mary