> Russ, > > I have a source statement in my .cshrc that makes sure the 64 bit ifort is > being used. I added those flags anyway, just in case, and there was no > change. > > What's strange is that it makes a libnetcdff90 file, which contains these > functions, but it seems to be looking for them in the wrong place. If I add > the directory '/f90/.libs/libnetcdff90.a' to the LD_LIBRARY_PATH variable in > the appropriate Makefile, it checks out with no problem. I've verified that > if I manually copy this to my /usr/lib, my other software calling on netCDF > nf90 functions has no troubleâ Here's another possibility. Try setting the environment variable mentioned here before running configure: http://www.unidata.ucar.edu/software/netcdf/docs/known_problems.html#intel-fortran-macosx Namely "lt_cv_ld_force_load=no". I'm not sure why it would be needed, but it's solved some problems compiling with ifort on MacOS-X previously ... --Russ > Sean > > ====================================== > Sean Crowell > Postdoctoral Research Associate > College of Atmospheric and Geographic Sciences > University of Oklahoma > Office: NWC 5420 > Phone: (405)325-1089 > address@hidden<mailto:address@hidden> > > > > > > On Sep 10, 2012, at 3:28 PM, Unidata netCDF Support wrote: > > Hi Sean, > > I'm trying to install NetCDF 4.2.1.1, which has the separate C and Fortran > Libraries. Separate from the HDF4 problem I emailed earlier, I'm having > difficulties with the Fortran Libraries. I get this error message: > > libtool: link: ifort -I../fortran -I../f90 -I../f90 -g -o .libs/f90tst_vars > f90tst_vars.o -L/usr/local/lib ../fortran/.libs/libnetcdff.dylib > /usr/local/lib/libnetcdf.dylib /usr/local/lib/libhdf5_hl.dylib > /usr/local/lib/libhdf5.dylib -lm -lz > 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 > > when I attempt make check. Any idea what's going on? I attached the full > output below. > > I see you're using the "-m64" option to gcc to indicate compiling for64-bit, > but you aren't > using a similar flag for the ifort compiler. Try specifying FCFLAGS="-m64" > and FFLAGS="-m64" > to configure before building the Makefiles. > > --Russ > > > ====================================== > Sean Crowell > Postdoctoral Research Associate > College of Atmospheric and Geographic Sciences > University of Oklahoma > Office: NWC 5420 > Phone: (405)325-1089 > address@hidden<mailto:address@hidden> > > > > > > > > > Russ Rew UCAR Unidata Program > address@hidden<mailto:address@hidden> > http://www.unidata.ucar.edu > > > > Ticket Details > =================== > Ticket ID: API-346739 > Department: Support netCDF > Priority: Normal > Status: Closed > > > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: API-346739 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.