Opened 19 years ago
Closed 19 years ago
#32 closed defect (wontfix)
ROPP unsupportable with ifort on Cygwin
| Reported by: | Dave Offiler | Owned by: | Dave Offiler |
|---|---|---|---|
| Priority: | trivial | Milestone: | |
| Component: | ROPP (all) | Version: | 0.8 |
| Keywords: | ifort, Intel, Cygwin, Windows | Cc: |
Description
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 <prog>.exe not <prog> [netCDF configure can handle this]
2) ifort/cl output <prog>.obj not <prog>.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<dir> -l<name> switches nor recognise lib<name>.a as an object library - expecting <name>.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.
