Saulo, I also see a presentation on using HDF4 with netCDF from several years ago that had slide 19 with the following bullet text: - This feature cannot be used at the same time as HDF4's netCDF v2 API, because HDF4 steals the netCDF v2 API function names. So you must use --disable-netcdf when building HDF4. (It might also work to âdisable-v2 for the netCDF build.) I don't know if the problem you are seeing is related to this, but it may be a good idea to build the HDF4 library using the --disable-netcdf option to the configure script. --Russ > Hi Saulo, > > Sorry to have taken so long to respond to your question ... > > I've attached my config log in case it may help. > > Yes, it looks like the hdf4 library, which you have installed in > /usr/local/hdf4/lib/, > is not being searched. Could you try running the configure script again with > the > CPPFLAGS and LDFLAGS you used, but also adding the definition > > LIBS='-lmfhdf -ldf -lhdf5_hl -lhdf5 -lsz -lm -lz -lcurl' > > The "-lmfhdf -ldf" tell the linker to explicitly search the HDF4 libraries in > the > directories you specified in LDFLAGS. I don't know whether the configure > script is > supposed to do this automatically, but if so, it appears to have a bug. > > --Russ > > > address@hidden> wrote: > > > > > > > > Saulo Soares, > > > > > > Your Ticket has been received, and a Unidata staff member will review it > > > and reply accordingly. Listed below are details of this new Ticket. Please > > > make sure the Ticket ID remains in the Subject: line on all correspondence > > > related to this Ticket. > > > > > > Ticket ID: UYL-334118 > > > Subject: FAIL: run_tests.sh > > > Department: Support netCDF > > > Priority: Normal > > > Status: Open > > > > > > > > > > > > The NetCDF libraries are developed at the Unidata Program Center, > > > in Boulder, Colorado, funded primarily by the National Science Foundation. > > > > > > All support requests are handled by the development team. No dedicated > > > support staff are funded at this time. For this reason we cannot guarantee > > > response times, nor that we can resolve every support issue, although we > > > do our best to respond within 72 hours. > > > > > > It is in the nature of support requests that the same question is asked > > > many > > > times. We urge you to search the support archives for material relating to > > > your support request: > > > > > > http://www.unidata.ucar.edu/search.jsp?support&netcdf > > > > > > If you are having trouble building netCDF, please take a look at the > > > "Building NetCDF" page: > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/building.html > > > > > > or the (unfortunately somewhat out-of-date) NetCDF Build Troubleshooter > > > page: > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/troubleshoot.html > > > > > > Windows users should see the FAQ list: > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#windows_netcdf4_2 > > > > > > Complete documentation (including a tutorial, and sample programs in C, > > > Fortran, > > > Java, and other programming languages) can be found on the netCDF > > > Documentation page: > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/ > > > http://www.unidata.ucar.edu/software/netcdf/examples/programs/ > > > > > > If you resolve your issue through one of these methods, please send a > > > reply to > > > this email, letting us know that you no longer need support. This will > > > help > > > us spend more time on netCDF development. > > > > > > Best regards, > > > > > > Unidata User Support > > > > > > > > > > > Russ Rew UCAR Unidata Program > address@hidden http://www.unidata.ucar.edu > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: UYL-334118 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.