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

[netCDF #FPM-331111]: nc-config issue

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #FPM-331111]: nc-config issue
  • Date: Tue, 16 Nov 2010 09:03:59 -0700
Hi Jeff,

> Right now, nc-config doesn't give you the cppflags and ldflags for hdf5
> (or any of the other dependencies), just netcdf. The following change
> fixes this.
> 
> --- nc-config.in.orig   2010-11-12 06:18:18.000000000 -0700
> +++ nc-config.in        2010-11-12 06:27:47.000000000 -0700
> @@ -14,9 +14,9 @@
> cc="@CC@"
> cxx="@CXX@"
> fc="@FC@"
> -cflags=" -I${includedir}"
> +cflags=" -I${includedir} @EXTERN_CPPFLAGS@"
> fflags="@FFLAGS@ @MOD_FLAG@${includedir}"
> -libs="-L${libdir} @NC_LIBS@"
> +libs="-L${libdir} @NC_LIBS@ @EXTERN_LDFLAGS@"
> flibs="-L${libdir} @NC_FLIBS@"
> has_dap="@HAS_DAP@"
> has_nc2="@HAS_NC2@"

Thanks for these fixes, which we'll put in the next snapshot.  Apparently
things worked for us without these becasue we had HDF5 installed in the same
directory as the netCDF library when we were testing static builds.

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: FPM-331111
Department: Support netCDF
Priority: Normal
Status: Closed