Fixlet
Description:
FIxed the hack for the INSTALL macro. It was checking the "whole"
path to the install-sh script instead of if it was just a relative
path with install-sh at the end.
Solution:
Changed the test to match any relative path with install-sh at the
end. This assumes that the install-sh is the one we supply to them
(an assumption it was making before, really).
Platforms tested:
Gondolin, Linux
Fix
Description:
On machines which use the bin/install-sh script, it wasn't picking up
the install-sh script unless it was one directory depth away from it
(ie, it thought that it was in ../bin/install-sh, which isn't good
if, like with the documentation, it's in a deeper directory).
Solution:
Hacked it up so that, if it does use the broken relative-path schema,
then it will change it to use the $(top_srcdir) macro instead.
Platforms tested:
Linux
[is this a bug fix? feature? ...]
Description:
Changed the default settings for enable-production and enable-debug
to no and yes respective, for this development branch.
Platforms tested:
Modi4 parallel and eirene.
Code cleaning
Description:
Moved all gcc compiler flags into the config/gnu-flags file and re-added
the warning flags removed during the beta testing.
Platforms tested:
FreeBSD 4.2 (hawkwind)
Feature Fix
Description:
When user specifies the --disable-hsizet flag, we still warn them
about this when they use gcc 2.91.66.
Solution:
I moved the check above the place where it checks what version gcc
compiler it is. If they did specify the flag and it is a 2.91.66
compiler, then it won't print the message out.
Platforms tested:
Linux
Suppress warnings for release.
Description:
Took out the -Wconversion -Wredundant-decls warning flags for gcc until
after the tree is split.
Platforms tested:
Linux 2.2.16 (eirene)
Warning Reduction
Description:
Removed the -Wpointer-arith flag which complains about addintion with
void * pointers. This is a known gcc 2.95.2 annoyance.
There's still some issues with many str* warnings...not 7000, though.
Platforms tested:
Linux
Name change
Description:
Changed the names of the testh5toh4 and testh4toh5 scripts to the
"canonical" form -- testh4toh5.sh and testh5toh4.sh.
Platforms tested:
Linux
New configure feature.
Description:
The H5private.h header file was re-defining the strdup function on several
platforms, generating a warning.
Solution:
Detect if the system defines a strdup function and don't re-define it, if
so.
Platforms tested:
FreeBSD 4.2 (hawkwind), IRIX64-64 (modi4)
Bug fix
Description:
The zlib.h header check was skipped if it thought it had
found -lz already. That resulted in H5_HAVE_ZLIB_H not defined
which caused compression feature not compiled even though everything
else said it was in.
The --with-hdf4 was default to yes but configure had no clue where to
find them. A plain waste of time and affected ZLIB's searching later.
Solution:
Basically restored what it was before--checking the optional switch
of with-hdf4 first, then with-zlib. (with-hdf4 now defaults to no.)
Added a big chunk of comments explaining why these two options must
be checked in this order.
Changes applied to configure.in. Then ran autoconf to generate
configure.
Platforms tested:
eirene (default and with-hdf4), modi4-64-parallel (with-hdf4),
arabica (with-hdf4) and, gondoline. That is right, even tested
it out with gondoline (with-hdf4 too.) All except modi4 configured,
compiled and tested correctly. Modi4 died in the compiling of
src/H5Zdeflate.c but that was not due to the configure changes.
Prepare for 1.4.0beta1 release
README:
src/H5public.h:
Updated with 1.4.0beta1 version information.
configure.in:
Changed default setting to --enable-production --disable-debug.
configure:
Derived from configure.in via autoconf.
Platforms tested:
Eirene (linux) running just the configure command and compared
difference with previous configure output to verify expected
difference.
Bug fix
Description:
The last modification put an extra comma in the AC_CHECK_HEADERS
that would generate an bad configure file.
Solution:
Removed the comma.
Platforms tested:
Ran autoconf and verified it by comparing the same with
the current working configure file which has been tested.
Purpose:
Bugfix
Description:
Under SunOS 5.5 the symbol FIONBIO wasn't known when compiling
with the Stream VFD configured.
Solution:
This symbol is defined in the system header file <sys/filio.h>.
Here we check whether this header is available.
Platforms tested:
SunOS 5.5 (hatteras), SunOS 5.6 (thor.sistec.kp.dlr.de)
Bug Fix
Description:
Some platforms, when building static libraries, complain that
libc doesn't have dlopen and friends.
Solution:
libtool supports workarounds for this. The one used here may not
work, but it's an attempt to correct it. If it doesn't work, then
there's something going on which I'm not privvy to...
Platforms tested:
(untested as of yet)
* 2000-11-15 Robb Matzke <matzke@llnl.gov> (CC_VERSION)
The compiler is always expanded to a
full path name if possible. This feature enhancement was
requested by Mark Miller, LLNL.
Command-line name change
Description:
Changed --with-stream-vfd to --enable-strea-vfd to be more
consistent with what people expect from the --with-FOO and
--enable-FOO arguments.
Backward compatibility additions
Description:
Added "--enable-hdf5v1_2" flag to enable HDF5 v1.2 compatibility API
functions (H5Tget_member_dims & H5Tinsert_array) being built in the
library.
Platforms tested:
FreeBSD 4.1.1 (hawkwind)
Purpose:
Bugfix
Description:
Rename the [H5_]HAVE_STRUCT_SOCKLEN_T into [H5_]HAVE_SOCKLEN_T.
Solution:
As pointed out by Bill the socklen_t type isn't a structure if
is it defined by the system headers.
So we should better take out the _STRUCT_ from the defines.
Platforms tested:
Purpose:
Bugfix
Description:
Detect whether the 'struct socklen_t' type is defined in the
system include header files.
Solution:
Added an AC_TRY_COMPILE test for 'struct socklen_t' to the configure
script. This test is only executed if the Stream VFD is configured.
Also added detection of <sys/types.h> and <sys/socket.h> system
header files.
Platforms tested:
Solaris 2.6 and 2.7
IRIX64
Linux
Windows NT (command line configure with gcc and cl)
Buglet
Description:
Wasn't picking up specified directories for the run-time linking
stuff that libtools does.
Solution:
There was some confusion about how the regex stuff works with
scripts. It's not `.*' for any character by `*'...Fixed.
Platforms tested:
Arabica
Bug Fix...AGAIN!
Description:
The logic to create the DYNAMIC_DIRS macro was accepting such
things as -lnoop_stubs which would cause libtools to barf.
Solution:
I'm pretty sure I fixed this once before. The change was lost. I
now test to make sure that the flag I'm adding has a "-L" prefix
on it...
Purpose:
Detect whether the system has the netinet/tcp.h header file.
Description:
The Stream VFD uses setsockopt(2) to set TCP_NODELAY on an opened
socket. This constant is defined normally in netinet/tcp.h
except for GNU cc under Windows where this header doesn't exist.
Platforms tested:
Windows NT, GNU cc
Buglet Fix...kinda
Description:
The --enable-c++ flag is in there, but configure can't handle the
++ on the end.
Solution:
Changed it to --enable-cxx instead. N.B. This feature isn't
really needed yet since C++ isn't integrated with the library
proper.
Platforms tested:
Linux
Bug Fix
Description:
Broke on Arabica trying to export the SEARCH macro.
Solution:
Assigned to the SEARCH macro and then exported it.
Platforms tested:
Arabica.
Bug Fix
Description:
When running configure on subdirectories (like fortran/), looking
up how make implements SEARCHes failed.
Solution:
Exporting the SEARCH macro so that subdirectories don't have to
look for it.
Platforms tested:
Modi4.
Bug Fix
Description:
zlib was not being retrieved from the place specified by the user
even if the user used the --with-zlib flag.
Solution:
Removed the automatic inclusion of /usr/ncsa/* into the macros
and use the user-defined place to try to pickup the zlib. I'm
relying on the order of the -L flags in the compile line to
specify which libraries to look into first before going on to
look into the system libraries. If some compiler doesn't honor
the this order, yikes...
Platforms tested:
Linux
Purpose:
h4toh5 converter tool under tools
Description:
put flag h4toh5 and testh4toh5 into the configure file.
Solution:
[details about the changes, algorithm, etc...]
[Please as detail as you can since your own explanation is
better than others guessing it from the code.]
Platforms tested:
at eirene and arabica.
[machines you have tested the changed version. This is absolute
important. Test it out on at least two or three different platforms
such as Big-endian-32bit (SUN/IRIX), little-endian-32(LINUX) and
64-bit (IRIX64/UNICOS/DEC-ALPHA) would be good.]
Libtool bug
Description:
The AR macro wasn't being propagated to the libtool file
correctly. When libtool was being generated, it wasn't
recoginizing the AR that was set in the configure script.
Solution:
export the AR macro after it's set.
Platforms tested:
Linux
I introduced a small bug when trying to fix the zlib stuff.
Description:
-lz wouldn't be specified with the compile flags if it was found
while checking for the HDF4 library.
Solution:
Removed my bad check and replaced with a better one.
Platforms:
Linux, Solaris
Added new option --with-Stream-VFD.
Description:
The configure option --with-Stream-VFD[={yes}|{no}] is used
to configure HDF5 to build the Stream Virtual File Driver.
The default is not to build it.
Platforms:
all platforms
Cleaned up the configure file a bit.
Description:
There were a few small bugs having to do with checking if strings
were empty. Also needed to force paths to be absolute instead of
relative.
Solution:
I standardized string checking (test -z for an empty string and
test -n for a non-empty string). Also, if the user specifies a
relative path for any of the options, the configure now makes it
into an absolute path for both CPPFLAGS and LDFLAGS macros.
Platforms:
Solaris, Linux
macro didn't work on all systems. This fixes it.
This also introduces the ability to configure for fortran and c++. This
is not to be implemented yet, though!
command form (e.g., cc, gcc) and put that in the libhdf5.settings
file. This would help show exactly which compiler was used during
the configure stage. It may not be 100% "correct" in some cases
such as "configure done in one machine but compiling done in another."
