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.
Dave, I wrote: > OK, thanks, I'll send you something as soon as I have tried a few more > tests. ... OK, I just tried this test on Lion (Mac OS X 10.7.2) with a newly unpacked netCDF 4.1.3 distribution and it worked with no change to m4/libtools.m4: $ lt_cv_ld_force_load=no FC="ifort" CXX="" CC="cc" LDFLAGS=-L/share/russ/local/mort/lib CPPFLAGS=-I/share/russ/local/mort/include ./configure && make -j check All the tests passed, including all Fortran tests. I'm using ifort version 12.1.0 (20111011), if that makes any difference, and an older version of Xtools, because I've not been able to successfully install the latest XTools on my Intel Core 2 Duo, so the cc I'm using is Apple's /usr/bin/cc version 4.2.1 (LLVM build 2335.6). Does using the lt_cv_ld_force_load=no environment variable work for you on an unmodified netcdf-4.1.3? I set CXX="" becasue I'm seeing an error in the old C++ API that's not relevant to this Fortran problem ... --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: YVQ-214480 Department: Support netCDF Priority: Normal Status: Closed