[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #WZH-305969]: Building netcdf-fortran with intel compilers fails

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.

  • Subject: [netCDF #WZH-305969]: Building netcdf-fortran with intel compilers fails
  • Date: Fri, 18 Dec 2015 17:10:06 -0700
Hello,

Unfortunately, I do not have access to the Intel compilers to try to recreate 
this issue myself.    I found the following resource for using the Intel 
compilers, located at the Intel developer zone:

* 
https://software.intel.com/en-us/articles/performance-tools-for-software-developers-building-netcdf-with-the-intel-compilers

That said, it has also been the case where adding '-DpgiFortran' flag to 
CPPFLAGS has helped other users; apparently, while obviously designed for use 
with the PGI Fortran compiler, this flag is also understood by the Intel 
compiler.

I'm sorry that I cannot provide more concrete help,

-Ward



> Hello,
> 
> I'm building netcdf-fortran-4.4.2 with intel compilers. Previously
> netcdf-4.3.3.1 was built without errors.
> 
> The process is:
> $ source compilervars.csh intel64
> $ configure --prefix=$HOME/intellibs
> $ make
> $ make check
> 
> The make check output fails:
> ....
> ============================================================================
> Testsuite summary for netCDF-Fortran 4.4.2
> ============================================================================
> # TOTAL: 5
> # PASS:  4
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See nf_test/test-suite.log
> Please report to address@hidden
> ...
> 
> Then, the nf_test/test-suite.log reports:
> ...
> *** testing nf_set_default_format ...
> bad default format: status = %dNo error
> 
> ###            2  FAILURES TESTING nf_set_default_format! ###
> Total number of failures:            2
> 2
> FAIL nf_test (exit status: 2)
> 
> Any suggestion?
> Thanks,
> Omar.
> 
> 
> 

Ticket Details
===================
Ticket ID: WZH-305969
Department: Support netCDF
Priority: Normal
Status: Closed