when you configure libtool with --disable-static, these two unittests fail:
	runpath-in-lalib.at
	need_lib_prefix

if you hack the libtool script to set build_old_libs=yes by default, then the 
unittests pass.  it looks like libtool has flags to enable building of either 
static or shared libs, but there's no way to make it build both (which is the 
default with --enable-{shared,static}).

along those lines, it'd be nice if --disable-static didn't do this to the local 
copy of libtool that gets installed.  i understand the relationship between the 
configure flags and the generated libtool script -- normally you use the local 
libtool build the local libs and then only install those libs.  this is even how 
it's used with libltdl.  but the libtool package itself is a bit special in that 
it also installs the libtool script.

in Gentoo atm, i'm hacking this by setting build_old_libs=yes in the generated 
libtool script before testing/installing.  but ideally it'd be possible to 
install `libtool` with settings based on what the system can do, not how the 
package is building libltdl.{a,so}.
-mike