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.
Hi Terry, Sorry it has taken so long to respond to your question ... > I am trying to build ECHAM5 on IBM-P550(AIX5.3+netcdf3.6.2) but am having > some netcdf library issues at the very end of my build as follows, > > -L../lib -lsupport -llapack -lblas -L/usr/lib/mass -lmass -lmassv > -L/home1/shizg/netcdf64/lib -lnetcdf > Ld: 0711-317 ERROR: Undefined symbol: .nf_enddef_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_strerror_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_inq_varname_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_put_var_double_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_put_vara_double_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_get_vara_double_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_get_var_double_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_put_att_double_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_get_att_double_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_put_att_int_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_get_att_int_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_put_att_text_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_get_att_text_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_def_var_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_inq_varid_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_inq_dimlen_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_inq_dimid_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_def_dim_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_open_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_close_ > Ld: 0711-317 ERROR: Undefined symbol: .nf__open_ > Ld: 0711-317 ERROR: Undefined symbol: .nf__create_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_set_fill_ > Ld: 0711-317 ERROR: Undefined symbol: .dgemm_ > Ld: 0711-317 ERROR: Undefined symbol: .dsyev_ > Ld: 0711-317 ERROR: Undefined symbol: .dgeev_ > Ld: 0711-317 ERROR: Undefined symbol: .dgesv_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_sync_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_put_var_int_ > Ld: 0711-317 ERROR: Undefined symbol: .dgetrf_ > Ld: 0711-317 ERROR: Undefined symbol: .dgetri_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_inq_varndims_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_inq_vardimid_ > Ld: 0711-317 ERROR: Undefined symbol: .nf_inq_nvars_ > Ld: 0711-317 ERROR: Undefined symbol: .dgemv_ > Ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more > information. > Gmake[1]: *** [../bin/echam5] Error 8 > Gmake[1]: Leaving directory `/home1/shizg/test/echam_5.3.02_ham_rev042/src' > Exit status from make was 2 > Gmake: *** [all] Error 2 > > The paths of netcdf lib and include files are correct. What is causing such > errors? Any suggestions will be greatly appreciated. Thanks! > > BTW: NCAR CCSM runs well on the same machine. Are you using the same Fortran compiler that was used when building the netCDF-3.6.2 library you have installed on your machine? Different Fortran compilers have different ways of calling C functions in the netCDF library, and this could be the source of the problem. Note that the GNU C compiler does not mix well with the AIX Fortran compiler. It's also possible that your netCDF library was built with a separate netCDF Fortran library, in which case you would need to specify -lnetcdff -lnetcdf instead of just -lnetcdf at the end of the compile line. Alternatively, you could download the latest netcdf-4.1.1 release from ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf.tar.gz and build that. If you specify --disable-netcdf-4 to the configure script, it only builds the netCDF-3 interfaces. That way you could specify the same Fortran compiler you are using and make sure it is compatible with the C compiler used to build the libraries. You would also get the new "nc-config" program, which makes it easier to know how applications should be built with the library. For example, invoking "nc-config --flibs" shows the library flags that should be used with the installation after it's built. Please let us know if this doesn't help ... --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: UTY-793114 Department: Support netCDF Priority: Urgent Status: Closed