summaryrefslogtreecommitdiffstats
path: root/tools/h5jam/Makefile.in
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch '1.8/master' of https://bitbucket.hdfgroup.org/scm/hdffv/hdf5 ↵lrknox2017-08-251-4/+2
|\ | | | | | | into hdf5_1_8
| * Disable building of libdynlib* dynamically loaded plugin test librarieslrknox2017-06-141-0/+1
| | | | | | | | | | | | | | on CYGWIN. Added known problem entry to RELEASE.txt. Set version for 1.8.19 release. Barbara updated contents of README.txt file.
| * Moved libdynlib* plugin test libraries to noist_LT_LIBRARIES with addedlrknox2017-06-121-4/+1
| | | | | | | | | | | | | | flag '-rpath /nowhere' to stop them being installed while keeping them from linking with libhdf5, etc. Incremented version to 1.8.19-pre1 and ran bin/release to create tar and zip files for testing.
* | generated reconfigure files for configure changesM. Scot Breitenfeld2017-08-041-0/+1
|/
* Change copyright headers to replace url referring to file to belrknox2017-05-161-6/+4
| | | | removed and replace it with new url for COPYING file.
* Move libdynlib* test lib files from lib_LTLIBRARIES to dyn_LTLIBRARIESlrknox2017-05-101-2/+5
| | | | | | and other changes to Makefiles and config/conclude.am to eliminate link errors with new libdynlib*_la_LDFLAGS which were added to stop libdynlib* files linking to external libraries.
* Update shared object file numbers according to changes in v1.8.18 release.lrknox2016-11-011-11/+23
| | | | | Update autotools and libtool versions. Run bin/reconfigure.
* [svn-r26728] Merge trunk reviwions 26669 and 26670.Larry Knox2015-04-041-1/+0
| | | | | | Removed from configure.ac VPATH section, LONE_COLON check and checks for redundant addition of /usr/include and /usr/lib to compile flags, with reconfigure. Tested h5committest
* [svn-r26697] HDFFV-9131: Remove obsolete/unneeded sections.Allen Byrne2015-04-011-2/+0
|
* [svn-r26582] Merge r26509 from trunkJerome Soumagne2015-03-251-2/+0
| | | | Run reconfigure after merges from autotools_rework branch
* [svn-r26395] Merges r26329 from trunkDana Robinson2015-03-091-5/+0
| | | | | | | | | | | | | | Removed the configure option that allows selective disabling of individual internal filters (fletcher32, shuffle, etc.). This feature mucked up the code with a lot of #ifdefs, saved very little space and was not scalable to a general scheme for library size reduction. We've decided to remove the feature while we investigate a more general scheme for decreasing the library size. Fixes: HDFFV-9086 Tested on: h5committest
* [svn-r26314] Brought autotools related changes from the trunk to the branch, ↵Scot Breitenfeld2015-02-261-1/+2
| | | | r26188 r26280
* [svn-r26304] bring 26303 from trunk:Mohamad Chaarawi2015-02-251-3/+3
| | | | remove files with .clog2 extension generated by MPE when doing make clean
* [svn-r26224] merge 26180 from trunk:vms_last_support_1_8Mohamad Chaarawi2015-02-181-1/+0
| | | | | | | | | | configure fixes for HDFFV-9068,9069,9096,9097,9135 from autotools_rework branch: - Remove Infering parallel compilers (C and Fortran) from configure.ac - Remove restriction to build shared with parallel - Cleanup parallel sections in configure.ac - remove large file support checks - MPE fixes.
* [svn-r25402] Bring 25397/8 from trunk:Mohamad Chaarawi2014-07-101-1/+0
| | | | | | | - remove configure checks for MPI_File_get_size and Big MPI_File_set_size as they are supported by MPIO implementations today. - fix bug in t_mpi.c (HDFFV-8856) tested with h5committest.
* [svn-r25106] Removed LT_ADD_LIBHDF5_DEPENDENCY configure conditional to roll ↵Larry Knox2014-04-251-1/+0
| | | | | | | | back fix for removing rpaths from lib files. The fix also removed dependencies on libhdf5, etc. when the --disable-sharedlib-rpath configure option was invoked. Added instead configure variable hardcode_into_lib=no. This removes rpath from lib files on Linux and solaris machines. Tested with h5committest on jam, koala, ostrich and platypus (cmake), and on emu and kite.
* [svn-r24980] HDFFV-8290: Merge automake 1.14.1 changes from trunkAllen Byrne2014-04-071-76/+461
| | | | Tested: h5committest
* [svn-r24878] Description:Quincey Koziol2014-03-241-1/+0
| | | | | | | | | | | | | | | | | | | | | Bring r24864 from trunk to 1.8 branch: Remove all traces of MPI-POSIX VFD and GPFS detection/code. Remove remaining traces of stream VFD. Remove testpar/t_posix_compliant test (it's not actually verifying anything). Clean up H5D__mpio_opt_possible() further. Moved environment variable that disables MPI collective operations into MPI-IO VFD (instead of it being in src/H5S.c). A few other small code cleanups. Tested on: Mac OSX/64 10.9.2 (amazon) w/parallel & serial (daily tested on trunk)
* [svn-r24732] Fix for reconfigure, which fails because ↵Larry Knox2014-02-221-0/+1
| | | | | | LT_ADD_LIBHDF5_DEPENDENCY is used in Makefiles but the declaration in configure.ac is missing. Copied declaration from trunk. Tested with h5committest on jam ostrich koala and platypus(cmake).
* [svn-r23324] Snapshot version 1.8 release 11 (snap11)HDF Tester2013-03-041-1/+1
|
* [svn-r22724] Convert tests to *.sh.in.Allen Byrne2012-08-281-15/+16
| | | | | | | | Convert configure.in to configure.ac. Align TESTS usage with autotools convention. Update all references from configure.in to configure.ac Tested: h5committest
* [svn-r22711] Updated autotools: autoconf 2.69, automake 1.12.3, m4 1.4.16, ↵Larry Knox2012-08-231-41/+95
| | | | | | libtool 2.4.2 Tested THG machines.
* [svn-r21421] Merged the Fortran 2003 changes from the trunk into the 1.8 ↵Scot Breitenfeld2011-09-271-0/+3
| | | | | | | | | | | branch, used: svn merge -r 20506:21414 https://svn.hdfgroup.uiuc.edu/hdf5/trunk/fortran Tested: jam (gnu, intel, pgi compilers) Also merged effected non-Fortran files: svn merge -r21247:r21248 https://svn.hdfgroup.uiuc.edu/hdf5/trunk/src/libhdf5.settings.in
* [svn-r21044] Purpose:Mike McGreevy2011-06-281-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix HDFFV-7592 "Remove PACKEDBITS option from autotools files" Description: The code for h5dump's packed bits feature was conditionally compiled in via this option during its 'beta' release in 1.8.5. Now that the feature is fully supported, h5dump has since been changed to always compile the packed bits code (having removed the #ifdef H5_HAVE_H5DUMP_PACKED_BITS checks), so this option in configure is no longer needed. This commit removes the --enable-h5dump-packed-bits configure option, including the help summary from './configure --help' and the libhdf5.settings output summary, the PACKED_BITS Makefile variable, and the definition of H5_HAVE_H5DUMP_PACKED_BITS define in appropriate pubconf header files (which has already been removed from use in source code as of r20722). Note that this option was never added to the trunk, thus this commit only need occur on the 1.8 branch. Tested: - Configure output, help, & summary verified on jam - h5committested
* [svn-r20889] Snapshot version 1.8 release 8 (snap1)HDF Tester2011-05-231-0/+1
|
* [svn-r20722] Refactor ext lib import and install.Allen Byrne2011-05-041-1/+0
| | | | | | | | Change case of tools subtests to not conflict with tools tests. Add SOVERSION for linux Remove PACKED BITS define/idef blocks Bring r20721 from trunk
* [svn-r20525] Description:Mike McGreevy2011-04-151-24/+49
| | | | | | | | Merge revisions 20475, 20502, and 20504 from trunk to 1.8 branch. Tested: Tested on jam, fred, bangan (CYGWIN), and h5committested.
* [svn-r19862] Updated libtool to version 2.4, autoconf to version 2.68, and ↵Larry Knox2010-12-011-0/+3
| | | | | | m4 to version 1.4.15. Tested with h5committest on amani, jam and heiwa.
* [svn-r19408] In this revision the '/' after ${DESTDIR} wherever it occursLarry Knox2010-09-161-5/+15
| | | | | | | | | | | | | | | | | | | | has been removed. According to the official description of DESTDIR by Gnu at http://www.gnu.org/prep/standards/html_node/DESTDIR.html, DESTDIR is prepended to the normal and complete install path that it precedes for the purpose of installing in a temporary directory which is useful for building rpms and other packages. The '/' after ${DESTDIR} will be followed by another '/' at the beginning of the normal install path. When DESTDIR is empty the path then begins with '//', which is incorrect and causes problems at least for Cygwin. The change made in config/commence.am affects many Makefile.*s when bin/reconfigure is run. EXAMPLEDIRs had to be corrected individually. Also the scripts to run examples after they are installed have checks added to see that the fortran and c++ directories are present before trying to run the scripts in them. Tested with h5committest on amani, heiwa and jam.
* [svn-r19371] Updated autoconf to version 2.6.7, libtool to version 2.2.10, ↵Larry Knox2010-09-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and m4 to version 1.4.14. Also added m4 directory for m4 macros according to autoconf suggestion. Tested with h5committest on amani, jam, and heiwa, and on linew. -This line, and those below, will be ignored-- M hdf5_1_8/test/Makefile.in A hdf5_1_8/m4 AM hdf5_1_8/m4/ltsugar.m4 AM hdf5_1_8/m4/libtool.m4 AM hdf5_1_8/m4/ltversion.m4 AM hdf5_1_8/m4/lt~obsolete.m4 AM hdf5_1_8/m4/ltoptions.m4 M hdf5_1_8/configure M hdf5_1_8/Makefile.in M hdf5_1_8/testpar/Makefile.in M hdf5_1_8/configure.in M hdf5_1_8/src/Makefile.in M hdf5_1_8/tools/Makefile.in M hdf5_1_8/tools/misc/Makefile.in M hdf5_1_8/tools/h5dump/Makefile.in M hdf5_1_8/tools/h5repack/Makefile.in M hdf5_1_8/tools/h5jam/Makefile.in M hdf5_1_8/tools/h5diff/Makefile.in M hdf5_1_8/tools/lib/Makefile.in M hdf5_1_8/tools/h5copy/Makefile.in M hdf5_1_8/tools/h5import/Makefile.in M hdf5_1_8/tools/h5stat/Makefile.in M hdf5_1_8/tools/h5ls/Makefile.in M hdf5_1_8/hl/test/Makefile.in M hdf5_1_8/hl/tools/Makefile.in M hdf5_1_8/hl/tools/gif2h5/Makefile.in M hdf5_1_8/hl/Makefile.in M hdf5_1_8/hl/src/Makefile.in M hdf5_1_8/hl/c++/test/Makefile.in M hdf5_1_8/hl/c++/Makefile.in M hdf5_1_8/hl/c++/src/Makefile.in M hdf5_1_8/hl/c++/examples/Makefile.in M hdf5_1_8/hl/fortran/test/Makefile.in M hdf5_1_8/hl/fortran/Makefile.in M hdf5_1_8/hl/fortran/src/Makefile.in M hdf5_1_8/hl/fortran/examples/Makefile.in M hdf5_1_8/hl/examples/Makefile.in M hdf5_1_8/config/commence.am M hdf5_1_8/MANIFEST M hdf5_1_8/c++/test/Makefile.in M hdf5_1_8/c++/Makefile.in M hdf5_1_8/c++/src/Makefile.in M hdf5_1_8/c++/examples/Makefile.in M hdf5_1_8/bin/ltmain.sh M hdf5_1_8/bin/reconfigure M hdf5_1_8/perform/Makefile.in M hdf5_1_8/fortran/test/Makefile.in M hdf5_1_8/fortran/testpar/Makefile.in M hdf5_1_8/fortran/Makefile.in M hdf5_1_8/fortran/src/Makefile.in M hdf5_1_8/fortran/examples/Makefile.in M hdf5_1_8/aclocal.m4 M hdf5_1_8/examples/Makefile.in
* [svn-r18836] Added code to config files, libhdf5.settings.in and ↵Larry Knox2010-05-171-0/+2
| | | | | | configure.in to add compiler version information for fortran and C++ in the settings file and the configure output for our common compilers on linux, solaris, and mac(gnu only). Tested: amani, jam, linew (h5committest) and with configure on these machines and tejeda.
* [svn-r18809] Purpose:Mike McGreevy2010-05-141-1/+1
| | | | | | | | | | | | | | | | | | | Fixed file cleanup during make distclean / make check. Description: The h5jam Makefile and the h5importtestutil.sh script both included cleanup steps that removed "*.txt" from the directory. This resulted in the new CMake specific configuration file, CMakeLists.txt, getting blown away by make distclean (for h5jam) and make check (for h5import). I've removed the *.txt from the h5jam Makefile as the directory looks to be getting cleaned appropriately without it, and I've modified the h5import script h5importtestutil.sh to point to the specific .txt files to clean. Tested: jam
* [svn-r18779] Add ${DESTDIR} to scripts and Makefiles so that make ↵Larry Knox2010-05-121-5/+5
| | | | | | DESTDIR=<install directory> install, installcheck and uninstall is supported for installing examples, since they are now installed as part of make install. This was necessary for rpmbuilds, but should also be supported otherwise. Tested: amani, jam, linew with committest, rpmbuild on jam and amani.
* [svn-r18710] Purpose:Mike McGreevy2010-05-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Improve configure's large-file support control. Description: Modified configure to now attempt to add defines necessary for supporting largefiles on all systems, instead of solely on linux. This is in response to user requests to enable largefile support on Solaris by default, as well as to give extra control on AIX (instead of just jamming the necessary flag into the config files). The old --enable-linux-lfs flag is being deprecated in favor of the --enable-largefile flag (enabled by default), which can be used on all platforms. --disable-linux-lfs can still be used to disable largefile support (on linux) when the --enable-largefile flag is not specified. On systems where large files cannot be supported in this manner, configure will report as such. Tested: h5committest AIX (NCSA's blue_print machine) duty, liberty, and linew.
* [svn-r18701] ID 1853:Albert Cheng2010-05-041-0/+1
| | | | | | | | Added the configure option --enable-h5dump-packed-bits for the h5dump optional feature. Tested: Jam (default and --disable-h5dump-packed-bits).
* [svn-r18580] Purpose:Mike McGreevy2010-04-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Autotool Upgrade / Libtool Bug Fix Description: Updated autotools referenced in bin/reconfigure as follows: Autoconf 2.64 --> Autoconf 2.65 Automake 1.11 --> Automake 1.11.1 Libtool 2.2.6a --> Libtool 2.2.6b-mcg The referenced libtool version is a custom version of 2.2.6b. It has been tweaked to fix a bug in libtool that occurs when using PGI 10.0 compilers. A check incorrectly categorizes the C++ compiler as version 1.0 instead of 10.0, and the link line is subsequently set up incorrectly and fails to compile. A patch has been made available and will be included in the next release of libtool, but in the meantime I've applied the patch to a custom installation as indicated above. This bin/reconfigure now references the custom installation, and the resulting configure script will correctly categorize the PGI 10.0 C++ compiler. Ran bin/reconfigure to regenerate configure and makefiles. Tested: jam and amani with PGI 10.0 compilers. h5committest
* [svn-r18106] bug 1673:Albert Cheng2010-01-121-4/+4
| | | | | | | | | | | | | | The mixed use of RUNTEST (original) and RUNTESTS (new) caused confusion. E.g., the timings in test/ was still using the old $RUNTEST. It made more sense to use $RUNTEST which is used by the dejagnu feature of automake. So, I changed all $RUNTEST or $RUNTESTS to $RUNEXEC. config/commence.am & config/conclude.am are the two files that got changes. Also fixed an error in test/Makefile.am. The rest are changed by bin/reconfigure. Tested: h5committested.
* [svn-r17645] Purpose:Mike McGreevy2009-10-151-9/+16
| | | | | | | | | | | | | | | Merge from Trunk Description: Merging all of my CFLAGS-related changes from trunk to 1.8 This includes revision #s: 17616, 17625, 17627, 17639, and 17643. Tested: h5committest and some additional checks on our FreeBSD as well as NCSA's machines.
* [svn-r17441] Purpose:Mike McGreevy2009-08-311-2/+12
| | | | | | | | | | | | | | | | | | | | | Merge from trunk Description: Merged revisions 17228 and 17440 from trunk to 1.8 Specifically, this brings support of --enable-static-exec flag into 1.8 Tested: Manually on jam, linew, smirom, liberty, plus h5committest. Currently, there is no automatic regression test that exists due to portability issues. Behavior is both different and undefined on certain systems (and while 'nm' command seems to exist on all machines, behavior is confirmed to be different on Mac, possibly others). Solution will be to set up some sort of framework in daily tests to build statically, remove shared paths, and verify executables can function.
* [svn-r17439] Purpose:Mike McGreevy2009-08-311-49/+97
| | | | | | | | | | | | | | | | | | | | | | Updating autotools Description: Bring revisions 17345 and 17357 from trunk to 1.8, specifically: - Automake upgraded to 1.11 - Autoconf upgraded to 2.64 - bin/reconfigure script edited to use new versions (on jam), and run to generate new configure script and Makefile.in's. - configure.in script edited to add "_cv_" to all AC_CACHE_VAL strings (in order to comply with new autoconf standard). - bin/install-sh script replaced with new version as provided by automake. Tested: - All issues on trunk were resolved, so only tested on jam and linew. Any other outliers should be caught by daily tests.
* [svn-r16793] Description:Mike McGreevy2009-04-201-4/+4
| | | | | | | | | | | | - Updated bin/reconfigure to use latest version of automake (1.10.2). Regenerated Makefile.in's by running bin/reconfigure. - Added libtool version numbers to c++, fortran, hl, hl c++, and hl fortran libraries. Tested: jam, liberty, smirom
* [svn-r16562] Purpose:Mike McGreevy2009-03-101-3/+3
| | | | | | | | | | | | | | | | | | Bug Fix Description: Fixing BZ #1381. The --includedir=DIR configure option, which is used to spceify installation location of C header files, did not work correctly as the path was hard-coded into config/commence.am. I'm presuming this is because an older version of automake didn't know where to put C header files. In any case, removing this line now defaults the includedir to the same directory that it is currently hard-coded to, and also fixes the configure flag which allows for customization of this value. Tested: jam, liberty
* [svn-r16519] merge 16518 from trunkPedro Vicente Nunes2009-02-261-0/+1
| | | | | | have 2 expected outputs for 2 h5ls runs depending if run on a big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output) the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other tested: jam, linew
* [svn-r15898] Purpose: Bug FixMike McGreevy2008-10-171-6/+1
| | | | | | | | | | | | | | | Description: Libtool wasn't working on linew because the script was not working with the Solaris Bourne shell. Libtool has built- in detection to ensure that it uses an appropriate shell, but our config/commence.am was hard coding this shell to be /bin/sh. Removing this line allows the shell to be picked up by configure, thus allowing libtool to use the correct shell on linew (bash). This was initially added to correct for a problem on an old machine (janus), so shoudn't be needed for machines we currently support. Tested: full make check install on kagiso and linew, compile only on smirom, duty, and liberty.
* [svn-r15881] Purpose: Bug Fixes, Libtool UpgradeMike McGreevy2008-10-151-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Description: 1) configure now sets LD_LIBRARY_PATH before checking for presence of SZIP encoder, so user does not need to set this. The path is then saved and sent to Makefiles, and used when "make check-install" is invoked, so user doesn't need to set this manually. 2) Upgraded libtool to version 2.2.6a 3) Rearranged tools build order as h5dump depends on existence of h5diff and h5import. Since h5dump is a sister directory as opposed to a parent of either, it doesn't know about the build rules of these tools, so setting any sort of explicit dependency confuses automake as it won't know how to build the tools. Instead, setting CONFIG = ordered forces an in-order traversal of each tools subdirectory. (without it will also traverse in order by default, but this should prevent gmake's -j option from jumping ahead as well). 'make check install' should now be able to be invoked after 'configure' without causing a dependency failure. 4) Removed H5_HAVE_LARGE_HSIZET macro from vms/src/h5pubconf.h, as this macro has now been out of the code for some time. (vms pubconf needs to be updated manually, which is why it was still hanging around). Tested: kagiso, smirom, liberty Note: h5diff looks to be causing failures in h5copy and h5dump tools tests, though these were present before any of my changes. My changes only affect build order and configuration setup, and shouldn't prevent fixes for these failures coming in after this checkin. Other than these, tests pass fine.
* [svn-r15042] Bug fix.Albert Cheng2008-05-201-4/+4
| | | | | | | | | | | | | | | | | | | Description: The fortran Makefile.am used HDF_FORTRAN to indicate it is part of the Fortran API source so that conclude.am will give fortran api prefix in the test output. The symbox HDF_FORTRAN is also used in configure for a different purpose (indicated --enable-fortran). They conflicted. Similar problem for the symbol HDF_CXX. Solution: Changed all the involved Makefile.am to use "FORTRAN_API" instead. It is a more appropriate name. Same for CXX_API. Along the way, discovered that the Makefile.am of hl/fortran/test and hl/cxx/test did not have those symbols at all. Added them in. Platform tested: Kagiso serial and h5committested (kagisopp, smirom, linew).
* [svn-r15033] Purpose:Albert Cheng2008-05-191-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improvement. Description: src/libhdf5.settings was the initial configure summary and is installed. Then configure is changed to dump a summary of the configure settings to the output and also append it to src/libhdf5.settings. That created two different output formats and duplicated information. This is the initial attempt to clean up this confusion and unify the output format. It is decided to use the src/libhdf5.settings template as the unified means. This requires more macros symbols be defined. The following symbols are all related to generating the src/libhdf5.settings file. AC_SUBST(EXTERNAL_FILTERS) AC_SUBST(MPE) MPE=no AC_SUBST(STATIC_EXEC) STATIC_EXEC=no AC_SUBST(HDF_FORTRAN) HDF_FORTRAN=no AC_SUBST(FC) HDF_FORTRAN=no AC_SUBST(HDF_CXX) HDF_CXX=no AC_SUBST(CXX) HDF_CXX=no AC_SUBST(HDF5_HL) HDF5_HL=yes AC_SUBST(GPFS) GPFS=no AC_SUBST(LINUX_LFS) LINUX_LFS=no AC_SUBST(INSTRUMENT) INSTRUMENT=no AC_SUBST(CODESTACK) CODESTACK=no AC_SUBST(HAVE_DMALLOC) HAVE_DMALLOC=no AC_SUBST(DIRECT_VFD) DIRECT_VFD=no AC_SUBST(THREADSAFE) THREADSAFE=no AC_SUBST(STATIC_SHARED) AC_SUBST(enable_shared) AC_SUBST(enable_static) AC_SUBST(UNAME_INFO) UNAME_INFO=`uname -a` The src/libhdf5.settings.in has CONDITIONAL's added to it too. The untrue conditions turned into a "#" and these lines are cleaned by the post processing script. Platform tested: h5committest on kagiso, smirom and linew. (smirom had failures not due to my changes.)
* [svn-r15006] Purpose: configure cleanupMike McGreevy2008-05-151-1/+0
| | | | | | | Description: cleaning up configure related to removal of --disable-hsizet flag, which we no longer support. Tested: kagiso
* [svn-r14824] Purpose: Updating HDF5 1.8 to use automake 1.10.1 and ↵Mike McGreevy2008-04-101-16/+20
| | | | | | | | | | | | | | | | | | libtool 2.2 Description: Updated bin/reconfigure script to reflect the new versions of libtool and automake in the /home1/packages/ directory. Rearranged configure.in script. For some reason, when using libtool 2.2, the libtool script doesn't generate until later in the configuration process, so I had to move a test that parsed through the libtool script to a point after where it was actually being generated. Ran libtoolize on the project, and ran bin/reconfigure to regenerate configure and Makefile.in's throughout. Tested: kagiso, smirom, linew, tg-login
* [svn-r14402] Description:Quincey Koziol2008-01-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add work-around to allow reading files that were produced with a buggy earlier version of the library, which could create objects with the wrong object header message count. There is now a configure flag "--enable-strict-format-checks" which triggers a failure on reading a file with this sort of corruption (when enabled) and allows the object to be read (when disabled). The default value for the "strict-format-checks" flag is yes when the "debug" flag is enabled and no when the "debug" flag is disabled. Note that if strict format checks are disabled (allowing objects with this particular kind of corruption to be read) and the file is opened with write access, the library will re-write the object header for the corrupt object with the correct # of object header messages. This closes bugzilla bug #1010. Tested on: FreeBSD/32 6.2 (duty) in debug mode FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Mac OS X/32 10.4.10 (amazon) in debug mode Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
generated by cgit v0.12 at 2024-11-22 22:15:16 (GMT)