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.
Morgan, > I am trying to install NCO and get an error message that has to do with > udunits so I have been trying to install udunits. I am able to run > ./configure fine, but when I run make I get an error message. I am a > student running this on our large linux cluster so I am only installing it > in my space and not on the whole system. Below I have included as much as > I could from what was listed in the INSTALL file. If you have any help I > would greatly appreciate it. I really need to get this working to be able > to use NCO. Thank you very much. > > Sincerely, > Morgan Silverman > > A) Linux login-1.beowulf.ncsu 2.4.21-37.0.1.ELsmp #1 SMP Wed Jan 11 > 18:44:17 EST 2006 i686 i686 i386 GNU/Linux > > B) 1.12.4 > > C) I don't have a file named configure.log > > D) config.log is attached > > E) I think this is the right compiler being used. /opt/gnu/compiler/bin > > F) I don't have a file make.log, but attached below is a log file which > contains the configuration and make at the bottom, which is where you can > see the error that is occurring. The configure(1) script wasn't told what argument-passing conventions to use when compiling C functions that are callable from Fortran routines. Please try the following: 1. Go to the top-level source-directory. 2. Execute the command "make distclean". 3. Ensure that the environment variable CPPFLAGS contains the string "-Df2cFortran" (or whatever macro definition is appropriate for your Fortran compiler), e.g., CPPFLAGS=-Df2cFortran; export CPPFLAGS The set of potential macros can be found in the examples of the file INSTALL in the top-level source-directory. 4. Execute the command "make". Redirect both the standard output and standard error streams to the file "make.log". 5. Execute the command "make test". Redirect both the standard output and standard error streams to the file "test.log". 6. Execute the command "make install". Redirect both the standard output and standard error streams to the file "install.log". Regards, Steve Emmerson Ticket Details =================== Ticket ID: EIP-914846 Department: Support UDUNITS Priority: Normal Status: Closed