RPMS available

These rpms have been built with the szip shared encoder for
CentOS6 and CentOS7 platforms (64-bit).
Source rpms, spec files, and the szip binary tar file used to produce 
these rpms are also available here.

There are now three HDF5 rpm packages:  the HDF5 base, devel, and
static packages.  The base package provides library files and tools.  The
devel package provides header files, scripts for compiling applications with
HDF5, and example code files for C, Fortran and C++.  The static package
provides static HDF5 lib files.  The devel and static packages are optional,
but they require previous installation of the HDF5 base package   

NOTE: When testing the rpms on 32 and 64 bit Fedora images in the
Amazon ec2 cloud, the image satisfied the rpm requirement for gcc-c++, but
the c++ examples were not correctly compiled. Running "yum install gcc-c++"
installed gcc-c++ and subsequently the c++ examples compiled and ran
correctly.

Installing

It is preferable to install rpms as the root user, because the commands are
simpler and the system rpm database will be used to check dependencies and
record the installation.  The basic command to do this is "rpm -Uvh <rpm package
file>".  If installing as the root user is impossible or undesirable, the rpms
in this directory are relocatable and may be installed by a non-root user with
two additional command line options.

The first additional option can be either --dbpath <path to directory for rpm
database files> or --root <path to alternate "/">.  The first of these options
may not be available in older versions of rpm.  Whichever option is chosen
will be required for all future rpm commands for these rpms.  The directory
specified for --dbpath must have write permission for the user and will be used
to store the rpm database files.  For the second option, the directory specified
must also have write permission for the user, and var/tmp, var/lock, and
var/lib/rpm should be created in the alternate directory as well as a file
var/lock/transaction ("touch transaction in the var/lock direcory).  The rpm
program will "chroot" to the alternate "/" directory and  the  database files
will be stored in the var/lib/rpm directory.

It should be possible though optional to copy the system rpm directory
(/var/lib/rpm) to the directory specified for --dbpath or to var/lib in the
directory specified for --root.  Doing this will allow the rpm to find
dependencies that are already installed on the system.  This database will not
be updated with future changes to software installed on the system.  If the
system rpm is not copied the rpm database will not know about libraries it has
not installed and will fail to install, listing the missing dependencies.  If
these missing dependencies are in fact present on the system the --nodeps
option can be added to the install command to bypass the dependency checker.

The second additional option can be either --prefix=<install directory> or
--relocate=/usr=<install directory> where the user has write permissions for
<install directory>.  The rpms will install files in the bin, include, lib or
lib64, and share subdirectories of this install directory instead of the
default /usr directory.

Here are some example commands using --dbpath and --prefix:

install command:         rpm --install --dbpath $HOME/rpm --prefix $HOME/usr
                              hdf5-1.8.N.N.with.szip.encoder.el6.x86_64.rpm

                         if required software listed is present on the system
                         repeating this command with --nodeps added will allow
                         the install to proceed.

check for hdf5 install:  rpm --query --dbpath $HOME/rpm hdf5
uninstall command:       rpm -e --dbpath $HOME/rpm hdf5