ExternalLibraries/HDF5 LIBSZ_DIR points to wrong place

Comments (8)

1. 

   Bruno Mundim reporter

   • changed status to open
   • removed comment

   • 2014-10-15T13:52:57+00:00
2. 

   Frank Löffler

   • removed comment

   I agree with the intention of the patch.

   However, this patch alone would cause problems with library directories not called 'lib', but for instance 'lib64'. I suggest to add a solution like the one used in other ExternalLibraries, e.g. HDF5: to search in both 'lib64', and 'lib' (in that order).

   • 2014-10-15T13:55:27+00:00
3. 

   Bruno Mundim reporter

   • removed comment

   Ok, good point. I will work on a similar solution then. Thanks!

   • 2014-10-15T14:05:04+00:00
4. 

   Bruno Mundim reporter

   • removed comment

   There are other issues in that configure.sh file as well. For example if we are building the HDF5 library then we use --with-zlib=${ZLIB_DIR} instead of what is suggested in their website, `--with-zlib=INCDIR,LIBDIR' (http://www.hdfgroup.org/ftp/HDF5/current/src/unpacked/release_docs/INSTALL), and we don't have the option --with-szlib=/Szip_Install_Directory set.

   Also note that ${ZLIB_DIR} is used when building but $LIBZ_DIR when checking if we should link against zlib library.

   To avoid further confusion and trying to stick to the perceived convention, wouldn't be better to rename LIBZ_DIR and LIBSZ_DIR to ZLIB_LIB_DIRS and SZLIB_LIB_DIRS, respectively? and maybe add the ZLIB_INC_DIRS to satisfy the requirement for configuring with `--with-zlib=INCDIR,LIBDIR' option?

   • 2014-10-16T05:31:34+00:00
5. 

   Erik Schnetter

   • removed comment

   Is there a particular problem you are trying to address?

   zlib is widely available, and Cactus can even build it. There is no real need to use szip these days.

   I have not encountered a problem when configuring HDF5 with zlib. This would only apply if we build HDF5 ourselves, but try to use an existing, non-standard zlib install. Since zlib is much faster to build than HDF5 this is not an important case in practice.

   • 2014-10-16T07:07:55+00:00
6. 

   Bruno Mundim reporter

   • removed comment

   Is there a particular problem you are trying to address?

   yes, preventing human beings like me from making silly mistakes :) I set LIBSZ_DIR to the library installation directory and the compilation aborted complaining it couldn't find the library. I looked at the configure script at HDF5 thorn and realized about the inconsistent notation. Just that. If we fix this notation we could prevent others in the future, including myself again, from making the same silly mistake, misled by this inconsistent notation, when preparing or updating machine option lists.

   • 2014-10-16T10:57:26+00:00
7. 

   Frank Löffler

   • changed status to open
   • removed comment

   removing "review" until there is a new patch.

   • 2014-12-08T09:21:32+00:00
8. 

   Ian Hinder

   • changed title to ExternalLibraries/HDF5 LIBSZ_DIR points to wrong place
   • removed comment

   • 2014-12-08T11:23:29+00:00
9. Log in to comment