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.
>To: address@hidden >cc: address@hidden >From: "Ronald W. Cook" <address@hidden> >Subject: cygwin - compiling problem >Organization: UCAR/Unidata >Keywords: 200109060345.f863jY110218 Hi, > I believe this problem stems from a failure to find a Fortran 90 > compiler and the failure of g77 as a substitute. I include the make > process and comparison of test files. If you're referring to the Cygwin problem: Making `test' in directory [build directory] .. cmp test.nc test_nc.sav test.nc test_nc.sav differ: char 1545, line 5 it has nothing to do with Fortran 90 or g77, because it occurs in a test involving only the C interface. The output you got from running the "configure" script: ... checking "g77" as Fortran-90 compiler... failed to build test program checking for xlf90... no checking for f90... no configure: warning: Could not find working Fortran-90 compiler configure: warning: The Fortran-90 interface will not be built is not an indication of an error. It just means you didn't use an environment variable to specify a Fortran 90 compiler. In this case the configure script looks around for some likely suspects but if none of them will properly compile a Fortran 90 program, it just continues with the build, skipping the step of building and testing a Fortran 90 interface. --Russ _____________________________________________________________________ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu