Hi Folks,
I ended up using the following script to inject static builds where needed.
Please pardon the ancient version of Bash installed on these machines :)
for f in {test,testpar,tools/*,perform,hl/*,hl/*/*}/Makefile
do
sed -i 's/CCLD = $(CC)/CCLD = $(CC) -static/g' $f
done
Cheers,
Aron
On Mon, Feb 3, 2014 at 2:59 PM, Aron Ahmadia <[email protected]> wrote:
> Hi Folks,
>
> Does anybody have any experience building shared libraries on the Cray XE6?
>
> I've been wrestling with HDF5 installation on a Cray XE6 today, and am
> having particular trouble getting the configure system to handle the
> sensitive needs of the Cray compilers.
>
> For example, to create a dynamically-linked executable, this requires the
> "-dynamic" flag to the Cray C compiler.
>
> cc -o test.exe -dynamic -lfoo
>
> I don't actually need hdf5 to build dynamic executables for me, what I
> really need is it to not fail when trying to build the test executables.
>
> There's a configure option that seems to allow the building of static
> executables,
>
> AC_ARG_ENABLE([static_exec],
> [AS_HELP_STRING([--enable-static-exec],
> [Install only statically linked executables
> [default=no]])],
> [STATIC_EXEC=$enableval])
>
> This then goes on to enable:
>
> LT_STATIC_EXEC="-all-static"
>
> This variable is used in quite a few places in the build tree, but it
> doesn't appear to be used at all in the ./test directory. Is this
> deliberate? The executables built here are susceptible to the same errors
> as elsewhere.
>
> My current inclination is to simply patch the flags in the ./test
> subdirectory to the (more appropriate) "-static" build flag, but I'm not
> very familiar with building a shared version of HDF5 on supercomputers.
> Any advice on how to move forward here would be appreciated.
>
> Cheers,
> Aron
>
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
