On 27 June 2017 at 08:24, ashwin .D <[email protected]> wrote: > I encountered no problems with make check in HDF5. So I went ahead and > installed it under /opt/local. Then I went downstream and compiled > netcdf-4.4.1 while pointing to the HDF5 installation under /opt/local and > could compile that as well. But when I did a make check on that one I got a > lot of HDF 5 related errors. So obviously my HDF5 compilation is not a done > deal yet. > > On Tue, Jun 27, 2017 at 4:52 PM, ashwin .D <[email protected]> wrote: > >> >* George, Matt and Carl. >> *>* Thanks much for all the suggestions. I >> *>* was able to move past the configure errors by using a combination of all >> *>* the tips you recommended. I in fact downloaded the hdf-1.10.1 version and >> *>* while running make did not give any problems I have a whole bunch of >> *>* redundant macro warnings and which when I looked up is identical to this >> *>* one - https://lists.hdfgroup.org/pipermail/hdf-forum_lists. >> <https://lists.hdfgroup.org/pipermail/hdf-forum_lists.> >> *>* hdfgroup.org/2010-July/003304.html >> <http://hdfgroup.org/2010-July/003304.html>. >> *>* I have enclosed a trimmed version of my logs. Is it good to proceed >> *>* forward or is there something I need to edit with the header files as >> well >> *>* ? Note these warnings do not occur with gfortran. >> *>>* Best regards, >> *>* Ashwin. >> *> >> >Sounds promissing. >> >> >The post you cite above encounters "PGC-S-..." lines, where the "-S-" >> >indicates a "Severe" error. Your log has "PGC-I-..." ("Information) and >> >"PGC-W-..." ("Warning") lines. These generally don't affect the operation >> >of the compiled code, but are things the developers may want to examine, >> >especially if they appear when compiling end-user code. You certainly want >> >to run "make check" (perhaps with HDF5TestExpress=0) and look over the >> >results carefully. On macOS with PGI I see: >> >> >Testing soft denormalized float -> double conversions >> >*WARNING* >> >[...] >> >maximum warnings reached, aborting test... >> >> >> >For hdf5-1.8.17, release_docs/INSTALL has a section "A.2. Building and >> >testing with PGI compilers" which says: >> >> >> > set the environment variable CXX to "pgCC -tlocal" >> >> Thanks I will definitely try that. But I have to let Carl and you know >> that I do not have a pgCC on my box. I only have a pgc++. I checked for a >> pgCC under my installation and I could not find it. >> What about modifying the header files as indicated in that post I linked >> ? >> > The changes to the header files should just hide the redundant defines, so shouldn't affect the compilation.
It looks like the "pgCC -tlocal" usage is for an older version of the PGI compilers. From an old PGI manual on the web, the -tlocal option is to make separate functions of each template instantiaion. The current pgi17ug_x64.pdf (page 135) says: "On Linux and macOS, the GNU-compatible pgc++ compiler uses the GNU g++ header files and Standard Template Library (STL) directly. The versions used are dependent on the version of the GNU compilers installed on your system, or specified when makelocalrc was run during installation of the PGI compilers. " > Are they not required ? >> > Hard to answer without seeing the errors for the netcdf compile, but in general, once you have hdf5 libraries that pass the tests, problems using the libraries are not fixed by changes in the hdf5 build. For those you may want to post on a netcdf forum. Although many people reading this list use netcdf, others who run into the same problems you are having when building netcdf will be looking for answers in netcdf forums, so for the sake of future users it is best to keep hdf5 separate from netcdf.
_______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org Twitter: https://twitter.com/hdf5
