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.
À̿켷, >Date: 12 Mar 2002 00:19:36 -0000 >From: "ÀÌ¿ ¼·" <address@hidden> >Organization: ? >To: address@hidden >Subject: Re:20020310: netCDF make test error on Linux >Keywords: 200203100058.g2A0wTa16842 The above message contained the following: > I can't make configure.log ,make.log, test.log and install.log Those files are created by your user shell when you redirect the standard output and standard error streams of the associated commands. If you can't create them, then you have a very serious problem with your operating system and I will not be able to help you. It seems more likely that you did not understand my request. I see from the file "config.log" that you did not use the C macro "f2cFortran": > configure:1933: checking if Fortran "byte" is C "signed char" <br> > configure:1942: cc -c -DNDEBUG -O conftest.c <br> This is probably the cause of your problem. Please try the following: 1. Go to the top-level source directory. 2. Perform steps 3 through 5 described near the end of the file INSTALL.html. 3. Ensure that the environment variable CPPFLAGS contains the string "-Df2cFortran". For example export CPPFLAGS='-Df2cFortran -DNDEBUG' or setenv CPPFLAGS '-Df2cFortran -DNDEBUG' depending on your user shell. There are examples of this for a Linux system in the file INSTALL.html. 4. Perform steps 6 through 9 described near the end of the file INSTALL.html. If you have problems, then you MUST send me the files described in the steps of the file INSTALL.html; otherwise, I will not be able to help you. If you do not understand or think that this is impossible, then please talk to someone who might know more about building packages on a Linux or UNIX system. Unless your system was made by the devil himself in a factory in hell, it is possible to create those files. :-) Regards, Steve Emmerson <http://www.unidata.ucar.edu>