id summary reporter owner description type status priority milestone component version resolution keywords cc 32 ROPP unsupportable with ifort on Cygwin Dave Offiler Dave Offiler "The Intel v8 F95 (ifort) and Microsoft C++.NET (cl) compilers on Windows are not supported by the netCDF configure system running under Cygwin. Issues: 1) ifort/cl output .exe not [netCDF configure can handle this] 2) ifort/cl output .obj not .o [autoconf has hooks for this, in parallel with .exe, but the netCDF configure does not use them. Result: configure fails to find expected conftest.o files]. A hack is possible, but mods to many autoconf input files are needed. 3) ifort/cl do not accept -L -l switches nor recognise lib.a as an object library - expecting .lib. Again, hacks to the autoconf files are possible. 4) Many expected .h files are not present for cl [copying e.g. gcc equivalents not an option - too many platform/compiler specific defines]; various fundamental functions like alloca not found or fail. (1) is not a problem; hacks for (2) & (3) implemented locally & work (but not supported by Unidata, so not a long-term solution); (4) is a show-stopper. Bottom line: netCDF cannot be built using ifort+cl on Windows platform. Nor (after contact with Unidata) is this situation going to change any decade soon. No netCDF = no ROPP_IO = no ROPP. Since very similar issues will affect other 'configure' type build systems (udunits and ROPP itself), this issue is wider than just netDCF support. Given the trivial user-base for this platform, never mind use of ifort+cl (netCDF with g95 & gfc under Cygwin is ok), no futher effort should be expended on supporting this combo. ROPP documentation should indicate that this combination is unsupported." defect closed trivial ROPP (all) 0.8 wontfix ifort, Intel, Cygwin, Windows