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

[netCDF #TLE-360648]: netcdf-fortran 4.4.4 compile error



Hello,

Unfortunately I'm not familiar with intel parallel studio; it clearly looks 
like a compiler issue, but I don't have an environment where I can try to 
recreate this problem.

The Intel documentation provides some instructions for compiling 
netCDF-Fortran, found at the following address:

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

It may be able to provide some additional information that I lack.

I'm sorry I can't provide a more immediately useful or applicable answer, but 
hopefully this information will be helpful!

Have a great day,

-Ward

> Hi all,
> I´m trying to build netcdf-fortran 4.4.4 with intel parallel studio xe 2016
> update 3 in Red Hat Enterprise Server 7.2, after install successfully
> Netcdf 4.4.1 and set all environment variables, following intructions from:
> http://www.unidata.ucar.edu/software/netcdf/docs/building_netcdf_fortran.html
> 
> It presents the following error when running make:
> 
> configure:4989: ifort -c   conftest.F >&5
> 
> conftest.F(3): error #5082: Syntax error, found END-OF-STATEMENT when
> expecting one of: => = . [ % ( :
> 
> choke me
> 
> ---------------^
> 
> compilation aborted for conftest.F (code 1)
> 
> configure:4989: $? = 1
> 
> configure: failed program was:
> 
> |       program main
> 
> | #ifndef __GNUC__
> 
> |        choke me
> 
> | #endif
> 
> |
> 
> |       end
> 
> config.log file is attached
> 
> Any ideas to fix this? Thanks for any help you can provide!
> 
> 


Ticket Details
===================
Ticket ID: TLE-360648
Department: Support netCDF
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.