+2004-07-29 Alexandre Duret-Lutz <adl@gnu.org>
+
+ * doc/libtool.texi (Tags): Document CC.
+ * m4/libtool.m4 (_LT_SETUP): Register CC as supported tag so that
+ Automake uses it.
+
2004-07-28 Gary V. Vaughan <gary@gnu.org>
Fix a long-standing bug where macro_version was always empty in
## ------------------------ ##
## Autoconf initialisation. ##
## ------------------------ ##
-AC_INIT([libtool], [1.5a], [bug-libtool@gnu.org])
+AC_INIT([libtool], [1.9b], [bug-libtool@gnu.org])
AC_CONFIG_HEADERS([config.h:config-h.in])
AC_CONFIG_SRCDIR([ltmain.in])
AC_CONFIG_AUX_DIR([config])
@multitable {Windows Resource} {Tag name}
@item Language name @tab Tag name
-@item C @tab
+@item C @tab CC
@item C++ @tab CXX
@item Java @tab GCJ
@item Fortran 77 @tab F77
@code{--tag=@var{tag}} option (@pxref{Invoking libtool}). It is a good
idea to do so in @file{Makefile} rules, because that will allow users to
substitute the compiler without relying on @command{libtool} inference
-heuristics. Note that there is no tag for @code{C} because that is
-the default configuration.
+heuristics. When no tag is specified, @command{libtool} will default
++to @code{CC}; this tag always exists.
Finally, the set of tags available in a particular project can be
retrieved by tracing for the @code{LT_SUPPORTED_TAG} macro (@pxref{Trace
test "x$enable_libtool_lock" != xno && enable_libtool_lock=yes
# Use C for the default configuration in the libtool script
+LT_SUPPORTED_TAG([CC])
_LT_LANG_C_CONFIG
_LT_LANG_DEFAULT_CONFIG
_LT_CONFIG_COMMANDS