We were moving to another office, now I've returned to work on WRF compiling.<br><br>Thanks all for tips. Seems like suggested solution with symlinks worked, I don't get configure error anymore.<br><br>Anyway, I think using 2 environment variables for NetCDF will improve portability and <span id="result_box" class="short_text" lang="en"><span title="Нажмите, чтобы увидеть альтернативный перевод" class="hps">convenience.</span></span> If sources and online tutorial will be fixed in this way, new user will not waste time on searching error and googling. If my reasoning are correct, maybe I should contact WRF developers?<br>
<br><div class="gmail_quote">2011/2/15 Kevin Matthew Nuss <span dir="ltr"><<a href="mailto:wrf@nusculus.com">wrf@nusculus.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br><br>Perhaps this would work (or not):<br><br>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.<br>
<br>mkdir myNetcdf<br>cd myNetcdf<br>ln -s /usr/include/netcdf-3/ include<br>ln -s /usr/lib64 lib<br>export NETCDF=`pwd`<br><br>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.<br>
<font color="#888888">
<br>Kevin<br><br></font><div class="gmail_quote"><div><div></div><div class="h5">On Sat, Feb 12, 2011 at 4:15 AM, Dmitry Vinokurov <span dir="ltr"><<a href="mailto:df6.626@gmail.com" target="_blank">df6.626@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5">
Hi!<br><br>I'm trying to compile WRF 3.2.1 on CentOS 5.5 (netcdf packages from rep) and get following error after ./configure:<br>----<br>grep: /usr/include/netcdf.inc: No such file or directory<br>----<br>NETCDF environment variable is set to "/usr", so as I understand WRF expect includes to be in "${NETCDF}/include" etc.<br>
<br>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".<br><br>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.<br>
<br>Thanks.<br><br>--<br>Best regards,<br><font color="#888888">Dmitry Vinokurov<br>
</font><br></div></div><div class="im">_______________________________________________<br>
Wrf-users mailing list<br>
<a href="mailto:Wrf-users@ucar.edu" target="_blank">Wrf-users@ucar.edu</a><br>
<a href="http://mailman.ucar.edu/mailman/listinfo/wrf-users" target="_blank">http://mailman.ucar.edu/mailman/listinfo/wrf-users</a><br>
<br></div></blockquote></div><br>
</blockquote></div><br>