From 430cf7470876424eb17c2690aaae97027a6d5beb Mon Sep 17 00:00:00 2001 From: Mike McGreevy Date: Wed, 4 Nov 2009 09:40:49 -0500 Subject: [svn-r17821] Purpose: Updating RELEASE.txt Description: Clarifying explanation of --enable-static-exec behavior. Tested: Doc only, none needed. --- release_docs/RELEASE.txt | 25 +++++++++++-------------- 1 file changed, 11 insertions(+), 14 deletions(-) diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt index 7ef5a77..2c592d9 100644 --- a/release_docs/RELEASE.txt +++ b/release_docs/RELEASE.txt @@ -129,10 +129,10 @@ Bug Fixes since HDF5-1.8.3 are not being compiled, respectively, so configure will not run some of the compiler tests for these languages when they are not being used. MAM - 2009/10/01 - - The --enable-static-exec flag has been fixed and will now install - statically-linked executables within the install directory when used - on systems that support the -static linker flag. - MAM - 2009/08/31 - BZ #1583 + - The --enable-static-exec flag will now properly place the -static flag + on the link line of all installed executables. This will force the + executable to link with static libraries over shared libraries, provided + the static libraries are available. MAM - 2009/08/31 - BZ #1583 - The PathScale compiler (v3.2) was mistaken as gcc v4.2.0 but it fails to recognize some gcc options. Fixed. (see bug 1301). AKC - 2009/7/28 - @@ -477,16 +477,13 @@ Known Problems commands. First, ask your system administrator to clean them out. Lastly, request IBM to provide a means to run poe without the debug socket. -* The --enable-static-exec configure flag fails to compile for Solaris - platforms. This is due to the fact that not all of the system libraries on - Solaris are available in a static format. - - The --enable-static-exec configure flag also fails to correctly compile - on IBM SP2 platforms for serial mode. The parallel mode works fine with - this option. - - It is suggested that you do not use this option on these platforms - during configuration. +* The --enable-static-exec configure flag will only statically link libraries + if the static version of that library is present. If only the shared version + of a library exists (i.e., most system libraries on Solaris, AIX, and Mac, + for example, only have shared versions), the flag should still result in a + successful compilation, but note that the installed executables will not be + fully static. Thus, the only guarantee on these systems is that the + executable is statically linked with just the HDF5 library. * There is also a configure error on Altix machines that incorrectly reports when a version of Szip without an encoder is being used. -- cgit v0.12