* doc/libtool.texi: Remove obsolete references to ltconfig.
* bootstrap: Don't bother creating an empty ltconfig and then
removing it.
* tests/quote.test: s/ltconfig/$0/
config.*
libtool
ltmain.sh
-ltconfig
libtoolize
+2001-09-10 Gary V. Vaughan <gary@gnu.org>
+
+ From Brad <brad@comstyle.com>:
+ * doc/libtool.texi: Remove obsolete references to ltconfig.
+ * bootstrap: Don't bother creating an empty ltconfig and then
+ removing it.
+ * tests/quote.test: s/ltconfig/\$0/
+
2001-09-09 Gary V. Vaughan <gary@gnu.org>
From Brad <brad@comstyle.com>:
ln -s libtool.m4 acinclude.m4
# fake the libtool scripts
touch ltmain.sh
-touch ltconfig
touch libtoolize
$ACLOCAL
$AUTOMAKE --gnu --add-missing --copy
cd ..
done
-rm -f ltmain.sh ltconfig libtoolize Makefile
+rm -f ltmain.sh libtoolize Makefile
exit 0
@end defvar
@defvar LDFLAGS
-The flags to be used by @code{ltconfig} when it links a program. If
+The flags to be used by @code{libtool} when it links a program. If
this is not set, @code{AC_PROG_LIBTOOL} will not use any such flags. It
affects only the way @code{AC_PROG_LIBTOOL} runs tests, not the produced
@code{libtool}.
the details needed to reproduce the bug, and a brief description of why
you think the behaviour is a bug. Be sure to include the word
``libtool'' in the subject line, as well as the version number you are
-using (which can be found by typing @kbd{ltconfig --version}).
+using (which can be found by typing @kbd{libtool --version}).
@node Maintaining
@chapter Maintenance notes for libtool
# This shell has a builtin print -r that does the trick.
echo='print -r'
elif test -f /bin/ksh && test "X$CONFIG_SHELL" != X/bin/ksh; then
- # If we have ksh, try running ltconfig again with it.
+ # If we have ksh, try running $0 again with it.
CONFIG_SHELL=/bin/ksh
export CONFIG_SHELL
exec "$CONFIG_SHELL" "$0" --no-reexec ${1+"$@"}