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.
Hi Bob, > I am trying to install netcdf-4.1.1 on my home 27" iMac. It has a 4-processor > 2.8 GHz i7 > (8 threads), runs 10.6.4. I decided to take the "easy route" and install the > binary > distribution but ended up with the results shown in "make #1". I had run into > this problem > before with my own libNamelist.a library, so I knew more or less what had to > be done. > > At this point I should digress to warn that I may occasionally sound like a > sophisticated > user but when it comes to installing libraries, nothing could be further from > the truth. > My makefile expertise is non-existant, so please make no assumptions about > its correctness. > > I assume there is no 64-bit binary available, so I switched to the source > code distribution, > netcdf.tar. I proceeded as follows: Right, we only have access to an i386 Mac OS X platform, and although we could use that to build an x86_64 binary, I don't think we could test it. > In directory ~/Downloads/ > tar -xvf netcdf.tar > > In directory ~/Downloads/netcdf-4.1.1/ > ./configure (no errors) see "cd #1" > make check (no errors) > make install (no errors) You cd #1 only had the first 8 lines of the configure output, but I'll assume it all looked good. > In directory /usr/local/lib/ > see "cd #2" > > At this point things look okay superficially. However I don't know what to > make of the files > "libnetcdf*.la" The ".la" extension identifies a text file created by GNU libtool, a tool that hides all the complexity of making and using shared libraries on different platforms. > In directory ~/Desktop/mpas2b++/ > make (errors) see "make #3" and "makefile" > > Help! I don't recognize any of the missing routines, so I presume they are > low level. I can > send you the code, although it is very rough at this stage. (I am working on > a C++ version > of the new MPAS ocean model, using OpenCL for parallelism. At least that's > the plan.) The missing routines are in the curl library, used to support the OPeNDAP client features of the new netCDF library. These features permit you to open and read from URLs of data on remote DAP servers, as well as local netCDF files. If you don't need this capability, you can build without it by specifying the configure flag --disable-dap. However, you may find this useful, in which case you need to add "-lcurl" to your link line in the Makefile. The curl utlity and libcurl already come with Mac OS X, so you don't have to build and install them separately. Because "make install" ran successfully, you now also have a utility program named "nc-config" in the same directory as the new ncgen and ncdump utilities. You can see what the library flags should look like, including the -lcurl option, by invoking "nc-config --libs". --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: OPB-517489 Department: Support netCDF Priority: Normal Status: Closed