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.
> > > > > > ----- Original Message ----- > > From: Unidata netCDF Support <address@hidden> > > Date: Sunday, July 22, 2007 5:18 am > > Subject: [netCDF #YKZ-923534]: failed configure for Netcdf > > To: address@hidden > > Cc: address@hidden > > > > > > Dear Unidata staff, > > > > > > > > I have failed to configure Netcdf-3.6.2 with my LF95 Fortran > > > compiler.> The diagnostic file config.log is attached. Some > > > compilation tests show > > > > 0 error and 0 warning, but still failure. I also tried the > > > > --disable-fortran-compiler-check option (just to see), but it > > > did not > > > > make a difference on the outcome (apparently, compilation checks > > > were> still run). This is uncharted territory on my part... > > > > > > > > Thank you for your help, > > > > > > > > Gerard > > > > > > > > > > > > > > > > > > > > Gerard C. Nihous, Ph.D. > > > > > > > > Hawaii Natural Energy Institute > > > > School of Ocean and Earth Science and Technology > > > > University of Hawaii at Manoa > > > > 1680 East-West Road, POST 122 > > > > Honolulu, Hawaii 96822 > > > > USA > > > > > > > > Phone: (808)-956-2338 > > > > Fax: (808)-956-2336 > > > > > > > > Email: address@hidden > > > > Web: www.hnei.hawaii.edu > > > > > > > > > > > > > Hawaii Natural Energy Institute > > School of Ocean and Earth Science and Technology > > University of Hawaii at Manoa > > 1680 East-West Road, POST 122 > > Honolulu, Hawaii 96822 > > USA > > > > Phone: (808)-956-2338 > > Fax: (808)-956-2336 > > > > Email: address@hidden > > Web: www.hnei.hawaii.edu > > > > > > > > Ahha! I bet that is the problem. > > The problem is, autoconf does not seem to have the concept of a C compiler which uses .o and a fortran compiler which uses .obj! > > It expects them to be the same. > > Is there any way, I wonder, to get Lahey Fortran to use .o instead of .obj? > > There does not seem to be a way to get gcc to use .obj, without extensive modification of the makefiles of the project. > > Thanks, > > Ed ...I believe I have the answer. Use the microsoft C compiler on your system to build netCDF, not the gcc which cygwin is finding for you. This will generate object files with the .obj extension, and not with the .o extension. The MS C compiler is called "cl.exe". You also need to have your env vars set properly in Cygwin to call the MS C compiler and have it work. I am not sure what those settings are. If you figure them out, please let me know. As you may know, there is a limited number of full-time engineers working on NetCDF - just me! So we rely on users to help port netCDF to new and interesting platforms, like cygwin with a commercial windows fortran compiler! In fact, I am struggling right now to set this up in my automatic testing environment. The hard part is getting all the env vars correct! Thanks, Ed Ticket Details =================== Ticket ID: YKZ-923534 Department: Support netCDF Priority: Normal Status: Open