[Wrf-users] NetCDF paths

[Dmitry N. Mikushin]

Hi,

Different distros often move around the stuff that goes in dev (devel)
packages, e.g. headers or static libraries. There is less deviation
with shared libraries, but still sometimes they are also kept under
subdirectiories, rather than in /usr/lib64, for example, mpich on red
hats is in /usr/lib64/mpich2/lib/ and will also fail with simple
-lmpich linking. So, *manual* adjustment of paths can't be fully
avoided, there are too many different situations. It should be better
to make configure script to perform some basic search and prompt for
input if one of multiple variants can be used. Also, ./configure can
use pkg-config to locate dependencies, if package provides .pc info.

- D.

2011/2/12 Dmitry Vinokurov <df6.626 at gmail.com>:
> Hi!
>
> I'm trying to compile WRF 3.2.1 on CentOS 5.5 (netcdf packages from rep) and
> get following error after ./configure:
> ----
> grep: /usr/include/netcdf.inc: No such file or directory
> ----
> NETCDF environment variable is set to "/usr", so as I understand WRF expect
> includes to be in "${NETCDF}/include" etc.
>
> Actually grep is right, there is no such file "/usr/include/netcdf.inc",
> NetCDF includes are located in "/usr/include/netcdf-3/" and libraries are in
> "/usr/lib64".
>
> The question is: is it possible to set separate paths for NetCDF includes
> and libraries? For example, Jasper uses $JASPERINC and $JASPERLIB variables
> and I think it'll be nice to work with NetCDF in the same way.
>
> Thanks.
>
> --
> Best regards,
> Dmitry Vinokurov
>
> _______________________________________________
> Wrf-users mailing list
> Wrf-users at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/wrf-users
>
>