Patch to update libtool in GCC and binutils trees
Steve Ellcey
sje@cup.hp.com
Thu Mar 29 23:01:00 GMT 2007
Following up to my own mail about problems using the new libtool in the
libstdc++-v3 directory, it looks like when the libstdc++-v3 configure
script runs:
if ${CONFIG_SHELL-/bin/sh} ./libtool --tag CXX --features |
grep "enable shared" > /dev/null;
then
LIBSUPCXX_PICFLAGS=-prefer-pic
else
LIBSUPCXX_PICFLAGS=
fi
the libtool executable has not yet been put in the libstdc++ object
directory. It does get put there later but at the time these commands
run, it has not yet been done. I am note sure who or how libtool winds
up in the build directory but it is obviously getting done later then
before and this is causing LIBSUPCXX_PICFLAGS to get set to NULL rather
than -prefer-pic.
I tried to replace "${CONFIG_SHELL-/bin/sh} ./libtool" with $LIBTOOL
which looks like it is getting set earlier in the configure script and
which should use the libtool from the top-level but that didn't work
either (LIBTOOL did not seem to be set). Does anyone have a better way
to handle this test in the libstdc++-v3 configure file? I don't see any
other libraries running libtool as part of the configure. Can I just
check the enable_shared variable instead?
Steve Ellcey
sje@cup.hp.com
More information about the Gcc-patches
mailing list