| +AC_DEFUN(AC_PROG_LIBTOOL,[AC_REQUIRE([_AC_PROG_LIBTOOL])
| +# If AC_PROG_CXX has already been expanded, run AC_LIBTOOL_CXX
| +# immediately, otherwise, hook it in at the end of AC_PROG_CXX.
| + AC_PROVIDE_IFELSE([AC_PROG_CXX],
| + [AC_LIBTOOL_CXX],
| + [define([AC_PROG_CXX], defn([AC_PROG_CXX])[AC_LIBTOOL_CXX
| +])])
| +#
| +# Quote A][M_PROG_GCJ so that aclocal doesn't bring it in needlessly.
| +# If either AC_PROG_GCJ or A][M_PROG_GCJ have already been expanded, run
| +# AC_LIBTOOL_GCJ immediately, otherwise, hook it in at the end of both.
| + AC_PROVIDE_IFELSE([AC_PROG_GCJ],
| + [AC_LIBTOOL_GCJ],
| + [AC_PROVIDE_IFELSE([A][M_PROG_GCJ],
| + [AC_LIBTOOL_GCJ],
| + [ifdef([AC_PROG_GCJ],
| + [define([AC_PROG_GCJ], defn([AC_PROG_GCJ])[AC_LIBTOOL_GCJ
| +])])#
| + ifdef([A][M_PROG_GCJ],
| + [define([A][M_PROG_GCJ], defn([A][M_PROG_GCJ])[AC_LIBTOOL_GCJ
| +])])])])])
The comments here are typically `dnl' comments: they address Autoconf
expansion issues. I have nothing against this personally, # is more
readable than dnl, but it is just so that you remember that this means
the comments will show up in `configure', in place where they will
make no sense.
The fact that you meant to talk about names of macros (hence `break'
them so that autoconf does not complain) is a clear sign of it.
