autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

26-fyi-doc-various.patch


From: Akim Demaille
Subject: 26-fyi-doc-various.patch
Date: Fri, 17 Aug 2001 13:50:49 +0200

Index: ChangeLog
from  Akim Demaille  <address@hidden>

        * doc/autoconf.texi: Work around Texinfo buglets.
        (Transformation Rules): One example is enough, users are expected
        to have their brains on. And BTW, use DESTDIR.
        (dvar): New macro.  Use it.

Index: doc/autoconf.texi
--- doc/autoconf.texi Fri, 17 Aug 2001 11:16:12 +0200 akim
+++ doc/autoconf.texi Fri, 17 Aug 2001 11:30:53 +0200 akim
@@ -14,6 +14,11 @@
 @address@hidden@r{]}
 @end macro

address@hidden A simple macro for optional variables with a default value.
address@hidden dvar{varname, default}
address@hidden@var{\varname\} = @address@hidden
address@hidden macro
+
 @c I don't like the way URL are displayed in TeX with @uref.
 @ifhtml
 @macro href{url, title}
@@ -1716,7 +1721,7 @@ @node Configuration Actions, Configurati
 @code{AC_CONFIG_COMMANDS} and @code{AC_CONFIG_LINKS}.  They all
 have this prototype:

address@hidden Can't use @ovar here, Texinfo 4.0 goes lunatic and emits 
something
address@hidden FIXME: Can't use @ovar here, Texinfo 4.0 goes lunatic and emits 
something
 @c awful.
 @example
 AC_CONFIG_FOOS(@address@hidden, address@hidden, address@hidden)
@@ -9223,8 +9228,10 @@ @node External Software, Package Options
 command line options to specify which such external software to use.
 The options have one of these forms:

address@hidden FIXME: Can't use @ovar here, Texinfo 4.0 goes lunatic and emits 
something
address@hidden awful.
 @example
address@hidden@ovar{arg}
address@hidden@var{arg}]
 address@hidden
 @end example

@@ -9300,8 +9307,10 @@ @node Package Options, Pretty Help Strin
 give @code{configure} command line options to specify whether to
 compile them.  The options have one of these forms:

address@hidden FIXME: Can't use @ovar here, Texinfo 4.0 goes lunatic and emits 
something
address@hidden awful.
 @example
address@hidden@ovar{arg}
address@hidden@var{arg}]
 address@hidden
 @end example

@@ -9521,29 +9530,17 @@ @node Transformation Rules,  , Transform
 @file{Makefile.in}:

 @example
-transform = @@program_transform_name@@
-install: all
-        $(INSTALL_PROGRAM) myprog $(bindir)/`echo myprog | \
-                                               sed '$(transform)'`
-
-uninstall:
-        rm -f $(bindir)/`echo myprog | sed '$(transform)'`
address@hidden example
-
address@hidden
-If you have more than one program to install, you can do it in a loop:
-
address@hidden
 PROGRAMS = cp ls rm
+transform = @@program_transform_name@@
 install:
         for p in $(PROGRAMS); do \
-          $(INSTALL_PROGRAM) $$p $(bindir)/`echo $$p | \
+          $(INSTALL_PROGRAM) $$p $(DESTDIR)$(bindir)/`echo $$p | \
                                               sed '$(transform)'`; \
         done

 uninstall:
         for p in $(PROGRAMS); do \
-          rm -f $(bindir)/`echo $$p | sed '$(transform)'`; \
+          rm -f $(DESTDIR)$(bindir)/`echo $$p | sed '$(transform)'`; \
         done
 @end example

@@ -11091,11 +11088,11 @@ @node Using Autotest, Questions, Obsolet
 @cindex Autotest

 @display
address@hidden: This section describes an experimental features which will
-officially part of Autoconf in a forthcoming release.  Although we
-believe Autotest is stabilizing, the documentation below describes an
-interface which might change in the future: do not depend upon Autotest
-without subscribing to the Autoconf mailings lists.}
address@hidden: This section describes an experimental feature which will
+be part of Autoconf in a forthcoming release.  Although we believe
+Autotest is stabilizing, this documentation describes an interface which
+might change in the future: do not depend upon Autotest without
+subscribing to the Autoconf mailing lists.}
 @end display

 It is paradoxical that portable projects depend on nonportable tools to
@@ -11272,7 +11269,7 @@ subshell.  It accepts a single argument,
 contents ought to end with an end of line.
 @end defmac

address@hidden AT_CHECK (@var{commands}, @ovar{status = 0}, @ovar{stdout}, 
@ovar{stderr})
address@hidden AT_CHECK (@var{commands}, @dvar{status, 0}, @ovar{stdout}, 
@ovar{stderr})
 @atindex CHECK
 Execute a test by performing given shell @var{commands}.  These commands
 should normally exit with @var{status}, while producing expected



reply via email to

[Prev in Thread] Current Thread [Next in Thread]