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.
Cara-Lyn, > To: address@hidden > From: "Cara-Lyn Lappen" <address@hidden> > Subject: netCDF General - mac OS 10.3.4 - cant get netcdf to make > Organization: UCAR/Unidata > Keywords: 200407231724.i6NHOqrY005658 The above message contained the following: > Institution: Colorado State University > Package Version: 3.5.1 > Operating System: mac OS 10.3.4 > Hardware Information: Mac > Inquiry: hello > > I have downloaded netcdf 3.5.1 from the unidata mirror site in Japan > (I was unable to get it from unidata directly). I unzipped it and tried > to install it. I am getting errors that I cannot correct. > > The first attachment is what I get when I run the configure script > (doesnt appear to be any errors). The second and third attachments are > what I get when I run "make". The second one is the standard output file > and the third one is the standard error file. All the attachments were empty (zero bytes). Would you please send items C through G described at http://my.unidata.ucar.edu/content/software/netcdf/INSTALL.html#ReportingProblems Please ensure that the files "configure.log" and "make.log" contain the simultaneous redirection of BOTH the standard output AND standard error streams rather than send the output from those streams separately. How this is done depends on your user-shell, for example Standard shells: make >make.log 2>&1 csh-like shells: make >&! make.log > Any help you could offer would be appreciated. > > -Cara-Lyn ... Regards, Steve Emmerson > NOTE: All email exchanges with Unidata User Support are recorded in the > Unidata inquiry tracking system and then made publically available > through the web. If you do not want to have your interactions made > available in this way, you must let us know in each email you send to us.