[Wrf-users] NetCDF paths

Kevin Matthew Nuss wrf at nusculus.com
Tue Feb 15 11:05:28 MST 2011


Perhaps this would work (or not):

Create your own NetCDF directory and simply have links, with the proper
names that point to the include and library directories that have the wrong
names. Then have $NETCDF point to your directory.

mkdir myNetcdf
cd myNetcdf
ln -s /usr/include/netcdf-3/ include
ln -s /usr/lib64 lib
export NETCDF=`pwd`

If it works, perhaps you could reply to the group. It seems like a problems
others might encounter. Otherwise, folks have to compile their own NetCDF
libraries just to get the correct directory structure. If it doesn't work -
sorry 'bout that.


On Sat, Feb 12, 2011 at 4:15 AM, Dmitry Vinokurov <df6.626 at gmail.com> wrote:

> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/wrf-users/attachments/20110215/547abcaa/attachment.html 

More information about the Wrf-users mailing list