[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[netCDF #PLO-158383]: NetCDF 4 Fortran compilation issues
- Subject: [netCDF #PLO-158383]: NetCDF 4 Fortran compilation issues
- Date: Fri, 31 May 2019 19:24:14 -0600
Pardon the delay in responding.
There is something very wrong with your source directory.
For example, in your make_check_log file, I see this:
> ftst_rengrps.F(13): error #5082: Syntax error, found IDENTIFIER 'NCLUDE' >
> when expecting one of: ( <END-OF-STATEMENT> ;
> implicit nonenclude
if I search ours for the string 'nonencode' I do not find it.
Let me start by suggesting that you throw away your current netcdf-fortran
source directory and re-download it just to make sure that it is not
corrupted.
>
> We are trying to compile NetCDF Fortran 4.4.5 and we have the problem
> described in make_check_log file attached to this email, but when we ran
> make alone, the build seems to be successful. Also, we attached the
> following files:
>
> config.log: configure output as requested in website.
> configure_log: console output of ./configure script.
> make_log: output of make command.
> make_check_log: output of make check command. This build is the one with
> the issue.
> nc-config_output: our NetCDF-C configuration.
>
> We are using the following compilers:
>
> [modelo@hn01 netcdf-fortran-4.4.5]$ ifort --version
> ifort (IFORT) 16.0.1 20151021
> Copyright (C) 1985-2015 Intel Corporation. All rights reserved.
>
> [modelo@hn01 netcdf-fortran-4.4.5]$ icc --version
> icc (ICC) 16.0.1 20151021
> Copyright (C) 1985-2015 Intel Corporation. All rights reserved.
>
> Thank you,
> Rodrigo
>
>
=Dennis Heimbigner
Unidata
Ticket Details
===================
Ticket ID: PLO-158383
Department: Support netCDF
Priority: Normal
Status: Open
===================
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.