summaryrefslogtreecommitdiffstats
path: root/windows
diff options
context:
space:
mode:
authorMike McGreevy <mamcgree@hdfgroup.org>2010-04-15 21:18:42 (GMT)
committerMike McGreevy <mamcgree@hdfgroup.org>2010-04-15 21:18:42 (GMT)
commit168c5c4a2c24abb75d643a515a2849d966ce4b27 (patch)
tree3dbdc92cac0114305ebc8c3d779e8c6ab4bf21a9 /windows
parentbbd47ad73873734c2fe05568ba6f676ac1f76e65 (diff)
downloadhdf5-168c5c4a2c24abb75d643a515a2849d966ce4b27.zip
hdf5-168c5c4a2c24abb75d643a515a2849d966ce4b27.tar.gz
hdf5-168c5c4a2c24abb75d643a515a2849d966ce4b27.tar.bz2
[svn-r18580] Purpose:
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
Diffstat (limited to 'windows')
0 files changed, 0 insertions, 0 deletions