Hi all,
There's been a problem with autoconf on AIX[45].x machines. It has to do
with the "hardcode_libdir_flag_spec" in the aclocal.m4 file. We have to
change things to this:
if test "$host_cpu" = ia64; then
hardcode_libdir_flag_spec='${wl}-R $libdir:/usr/lib:/lib'
allow_undefined_flag="-z nodefs"
archive_expsym_cmds="\$CC $shared_flag"' -o $output_objdir/$soname
${wl}-h$soname $libobjs $deplibs $compiler_flags ${wl}${allow_undefined_flag}
'"\${wl}$no_entry_flag \${wl}$exp_sym_flag:\$export_symbols"
else
#######################################################################
# This is a MAJOR HACK(tm) to get HDF5 to compile on Pacific Blue.
# The ``-b nolibpath -b ...'' flags were messing with the mpicc
# compiler's already defined library paths and it wasn't able to find
# the libraries it needed to run....DOH!
hname="`hostname`"
case "$hname" in
*pacific.llnl.gov* | *s0*)
hardcode_libdir_flag_spec=' '
;;
*)
hardcode_libdir_flag_spec='${wl}-bnolibpath
${wl}-blibpath:$libdir:/usr/lib:/lib'
;;
esac
#
# End MAJOR HACK
#
#######################################################################
# Warning - without using the other run time loading flags,
# -berok will link without error, but may produce a broken library.
allow_undefined_flag='${wl}-berok'
# This is a bit strange, but is similar to how AIX traditionally builds
# it's shared libraries.
archive_expsym_cmds="\$CC $shared_flag"' -o $output_objdir/$soname $libobjs
$deplibs $compiler_flags ${allow_undefined_flag} '"\${wl}$no_entry_flag
\${wl}$exp_sym_flag:\$export_symbols"' ~$AR -crlo $objdir/$libname$release.a
$objdir/$soname'
fi
The problem being that the linker will segfault if the ${wl}... line is
too long. There *has* to be a better way to do this than my hack above.
I'm using autoconf 2.53. Is this fixed in the next release? Is there a
better way to do this for the 2.53 branch?
Thanks.
--
|| Bill Wendling [EMAIL PROTECTED]
|| Coding Simian
