1) using macro in difinition macro.

autoconf.texi has macro @ovar{} and @dvar{}, which are used in
@defmac{} like below:

  @defmac AC_INIT (@var{package}, @var{version}, @ovar{bug-report},...

You know that `makeinfo -E' does not work in "Definition macro".  And
Info which came with texinfo-4.2 shows below in "Node: Def Cmd
Template" at last two lines:

    Note that, due to implementation difficulties, macros are not expanded
  in `@deffn' and all the other definition commands.

I think that such limitation can be ignored.  But some users maybe
complain :-).


2) use @@ for @. 

And I get patch from Koji Arai <[EMAIL PROTECTED]>.
====== from here ======
--- autoconf.texi.orig  2002-09-09 20:30:31.000000000 +0900
+++ autoconf.texi       2002-09-09 20:31:11.000000000 +0900
@@ -13668,8 +13668,8 @@
 
 AUTOTEST = $(AUTOM4TE) --language=autotest
 $(TESTSUITE): $(srcdir)/testsuite.at
-        $(AUTOTEST) -I $(srcdir) [email protected] -o [email protected]
-        mv [email protected] $@
+        $(AUTOTEST) -I $(srcdir) $@@.at -o $@@.tmp
+        mv $@@.tmp $@@
 @end example
 
 You might want to list explicitly the dependencies, i.e., the list of
@@ -13683,11 +13683,11 @@
 
 atconfig: $(top_builddir)/config.status
         cd $(top_builddir) && \
-           $(SHELL) ./config.status $(subdir)/$@
+           $(SHELL) ./config.status $(subdir)/$@@
 
 atlocal: $(srcdir)/atlocal.in $(top_builddir)/config.status
         cd $(top_builddir) && \
-           $(SHELL) ./config.status $(subdir)/$@
+           $(SHELL) ./config.status $(subdir)/$@@
 @end example
 
 @noindent
====== to here ======


3) AT_CONFIG was replaced, I think

In autoconf.info:
   - Use the `AT_CONFIG' macro from within file `configure.ac'.  This
     macro accepts one argument, which is the directory, relative to the
     test directory, where the executables are prepared.

But in ChangeLog:

  2001-08-27  Akim Demaille  <[EMAIL PROTECTED]>
       * m4/atconfig.m4 (AT_CONFIG): Remove, replaced by...

Please fix documentation.

Thanks

-- 
Nishio Futoshi <[EMAIL PROTECTED]>


Reply via email to