Ralf Wildenhues wrote:
Hmm. "Always use our own libtool" sounds a lot like some bug needed
this. But then again, that line has been in there unchanged for six
years. I wonder if it will break setups if we change this, it's like
a rope to save us from stupid errors rather than a necessity.
Anybody have good reasons against changing this?
Running the tests in an older libtool.m4 and then using a newer installed
libtool seems like a waste. If we want to do this, then we should probably
skip all of the libtool tests at configure time and print a warning that
LIBTOOL has been overridden in the environment.