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.
Carles,
I should have also pointed out that most of the error messages in config.log
are not of concern. They are generated while the configure script is
determining
the compilation environment, so it can generate the right commands to build from
source. The only configure message in your config.log file to be concerned with
is the last one:
configure:24263: ifort -o conftest -g conftestf.o conftest.o
ipo: warning #11009: file format not recognized for conftest.o
ld warning: in conftest.o, file is not of required architecture
Undefined symbols:
"_sub_", referenced from:
_MAIN__ in conftestf.o
ld: symbol(s) not found
configure:24266: $? = 1
configure:24289: error: Could not link conftestf.o and conftest.o
which indicates that the conftest.o, generated by the C compiler cc, cannot be
linked with conftestf.o, generated by the Fortran compiler ifort.
If you run the commands
file conftest.o
file conftestf.o
the results may tell you why the C compiler output is incompatible with the
Fortran compiler output. If you don't understand the output from these
commands,
send the results to us and maybe we can fgure out what is going on.
--Russ
Russ Rew UCAR Unidata Program
address@hidden http://www.unidata.ucar.edu
Ticket Details
===================
Ticket ID: ASW-719077
Department: Support netCDF
Priority: Normal
Status: Closed