libtool 1.5.22 passes ld options to gcc on ia64-hp-hpux11.23?

[Thomas Anders]

With libtool 1.5.22 and gcc 4.0.4/4.2.0 on ia64-hp-hpux11.23, I see
libtool passing "+b /some/path" directly to "gcc -shared" rather than
escaping it via "-Wl,":

hpbox# sh ../libtool  --mode=link gcc -rpath
/usr/local/lib -version-info 16:0:1 -o libnetsnmpagent.la *.lo
../snmplib/libnetsnmp.la
gcc -shared -Wl,+h -Wl,libnetsnmpagent.so.16
-Wl,+nodefaultrpath -o .libs/libnetsnmpagent.so.16.0
.libs/agent_handler.o .libs/agent_index.o .libs/agent_read_config.o
.libs/agent_registry.o .libs/agent_trap.o .libs/kernel.o
.libs/snmp_agent.o .libs/snmp_perl.o .libs/snmp_vars.o  +b
/tmp/test/snmplib/.libs ../snmplib/.libs/libnetsnmp.so -lc
gcc: +b: No such file or directory

configure-generated libtool contains:
CC="gcc"
LD="/usr/ccs/bin/ld"
hardcode_libdir_flag_spec="\${wl}+b \${wl}\$libdir"
hardcode_libdir_flag_spec_ld="+b \$libdir"
archive_cmds="\$CC -shared \${wl}+h \${wl}\$soname \${wl}+nodefaultrpath
-o \$lib \$libobjs \$deplibs \$compiler_flags"

Changing hardcode_libdir_flag_spec_ld to match hardcode_libdir_flag_spec
works around the issue.

Am I correct to assume that this is fixed in 1.5.24 due to the following
change?

2006-06-12  Ralf Wildenhues  <address@hidden>
        * ltmain.in (link mode): Disregard
        `hardcode_libdir_flag_spec_ld' if we're using `$CC' to link.
        * libtool.m4 () [ hpux10, hpux11; hppa*64*, ia64* ]
        <hardcode_libdir_flag_spec_ld>: Removed.
        Reported by Roger While <address@hidden>.


+Thomas