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.
Thanks for the logs, Li! Could you tell me the output from the following three commands: file /opt/ifort_libs/hdf5/1.8.6/lib/libhdf5.dylib file <build dir>/fortran/.libs/libnetcdff.dylib file <build dir>/fortran/.libs/libnetcdf.dylib Thanks! Sean > Dear Sean, > > The logs are in the attachments. > > Cheers, > > Li > > > > On Jun 4, 2011, at 1:00 AM, Unidata netCDF Support wrote: > > > Greetings Li, > > > > Would you mind sending your config, make, and make check logs? > > > > Thanks! > > > > Sean Arms > > > >> Dear all, > >> > >> I am trying to install NETCDF 4.1.2 with netcdf4 into our Mac Pro. The > >> fortran compiler is intel 12.0.0. The configure is: > >> > >> ./configure --prefix=/opt/ifort_libs/netcdf/4.1.2 --enable-netcdf4 > >> --with-hdf5=/opt/ifort_libs/hdf5/1.8.6/ FC=ifort > >> > >> When the "make" complete, I executed "make check". It complained: > >> > >> libtool: link: ifort -I../fortran -I../f90 -I../f90 -I../include > >> -I../liblib -I/opt/ifort_libs/hdf5/1.8.6//include -g -o .libs/f90tst_vars > >> f90tst_vars.o -L/opt/ifort_libs/hdf5/1.8.6//lib > >> ../fortran/.libs/libnetcdff.dylib ../liblib/.libs/libnetcdf.dylib -lcurl > >> /opt/ifort_libs/hdf5/1.8.6/lib/libhdf5_hl.dylib > >> /opt/ifort_libs/hdf5/1.8.6/lib/libhdf5.dylib -lm -lz > >> ld: warning: -macosx_version_min not specificed, assuming 10.6 > >> Undefined symbols for architecture x86_64: > >> "_netcdf_mp_nf90_create_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_def_dim_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_def_var_manydims_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_def_var_chunking_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_enddef_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_put_var_2d_fourbyteint_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_close_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_open_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_inquire_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_inq_var_chunking_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_get_var_2d_fourbyteint_", referenced from: > >> _MAIN__ in f90tst_vars.o > >> "_netcdf_mp_nf90_strerror_", referenced from: > >> _f90tst_vars_IP_handle_err_ in f90tst_vars.o > >> ld: symbol(s) not found for architecture x86_64 > >> make[2]: *** [f90tst_vars] Error 1 > >> make[1]: *** [check-am] Error 2 > >> make: *** [check-recursive] Error 1 > >> > >> And I found that there is no f90 symbols in "libnetcdff.dylib" by > >> executing "nm fortran/.lib/libnetcdff.dylib", but in "libnetcdff.a" in the > >> same directory. > >> > >> Help, please! > >> > >> Best regards, > >> > >> Li > >> > > > > > > Ticket Details > > =================== > > Ticket ID: RPI-910358 > > Department: Support netCDF > > Priority: Normal > > Status: Open > > > > > Ticket Details =================== Ticket ID: RPI-910358 Department: Support netCDF Priority: Normal Status: Open