+2010-10-30 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+ docs: mention shell requirement for libtool script.
+ * doc/libtool.texi (Invoking libtool): Document that the shell
+ used to invoke libtool needs to be the same used to configure
+ it.
+ * THANKS: Update.
+ Report by Markus Duft.
+
2010-10-15 Gary V. Vaughan <gary@gnu.org>
libtool: remove redundant unsubstituted shell var defaults.
Marc J. Fraioli fraioli@dg-rtp.dg.com
Marcel Loose loose@astron.nl
Mark Kettenis kettenis@phys.uva.nl
+ Markus Duft markus.duft@salomon.at
Matthijs Kooijman matthijs@stdin.nl
Micheal E. Faenza mfaenza@mitre.org
Michael Haubenwallner michael.haubenwallner@salomon.at
Print libtool version information and exit.
@end table
+The current @command{libtool} implementation is done with a shell script
+that needs to be invoked by the shell which @command{configure} chose for
+configuring @command{libtool} (@pxref{config.status Invocation, , The
+Autoconf Manual, autoconf, The Autoconf Manual}). This shell is set in
+the she-bang (@samp{#!}) line of the @command{libtool} script. Using a
+different shell may cause undefined behavior.
+
The @var{mode-args} are a variable number of arguments, depending on the
selected operation mode. In general, each @var{mode-arg} is interpreted
by programs libtool invokes, rather than libtool itself.