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.
Christopher, > I'm having problems installing the Unidata units library on my Linux > computer. The version of the unidata library I'm trying to install is > 1.12.4. The first attachment (uname.log) is the output from the "uname > -a" command. The second attachment is the log file for "./configure". > The third attachment is the log file for "make". The installation bombed > during the "make"command. Thank you very much in advance for your > assistance. > > Chris Mertens > > ------------------------------------------------------------------------ > Dr. Christopher J. Mertens > Senior Research Scientist > NASA Langley Research Center > Science Directorate, Chemistry and Dynamics Branch > 21 Langley Blvd., Mail Stop 401B > Hampton, Virginia 23681-2199 USA > Voice: +1-757-864-2179 > Fax: +1-757-864-6326 > Email: address@hidden > <mailto:address@hidden> > ------------------------------------------------------------------------ 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 "configure" script. Redirect both the standard output and standard error streams to the file "configure.log". 5. Execute the command "make". Redirect both the standard output and standard error streams to the file "make.log". 6. Execute the command "make test". Redirect both the standard output and standard error streams to the file "test.log". 7. 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: RSQ-889375 Department: Support UDUNITS Priority: Normal Status: Closed