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.
Jian, > I need your help in my installation of ldm. I followed the instruction to > the step to configure. It showed the configure is not successful in > config.log. I attached these two files. Hope you can help me to figure out > what the problem is. The file "config.log" contained the following: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by LDM configure 6.9.7, which was generated by GNU Autoconf 2.63. Invocation command line was $ ./configure ... The argument "..." caused the problem. That string (three periods) is a common western idiom that indicates that something else (perhaps nothing) should go where the string is: the three periods are not meant to be literally used. If you don't need any of the configure(1) script options, then you should invoke the configure(1) without any arguments. For example $ ./configure >/configure.log 2>&1 or $ ./configure >&! configure.log depending on your user-shell (sh(1)-like or csh(1)-like). Sorry for the confusion. > Thank you in advance, > > Jiang Regards, Steve Emmerson Ticket Details =================== Ticket ID: FQA-793348 Department: Support LDM Priority: Normal Status: Closed