doc fix: mention top_builddir / abs_top_builddir idiosyncracy

[Thien-Thi Nguyen]

2002-04-26  Thien-Thi Nguyen  <address@hidden>

        * doc/autoconf.texi: Mention that `top_builddir' and
        `abs_top_builddir' should not be used in the actual
        top-level build directory.      

(alternatively, autoconf needs to guarantee top_builddir is non-empty.)

thi

__________________________________
Index: autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.620
diff -u -p -w -c -r1.620 autoconf.texi
cvs server: conflicting specifications of output style
*** autoconf.texi       25 Apr 2002 15:32:15 -0000      1.620
--- autoconf.texi       27 Apr 2002 00:33:04 -0000
*************** Absolute path of @code{builddir}.
*** 2062,2073 ****
  @defvar top_builddir
  @ovindex top_builddir
  The relative path to the top-level of the current build tree.  In the
! top-level directory, this is the same as @code{srcbuild}.
  @end defvar
  
  @defvar abs_top_builddir
  @ovindex abs_top_builddir
! Absolute path of @code{top_builddir}.
  @end defvar
  
  @defvar srcdir
--- 2062,2074 ----
  @defvar top_builddir
  @ovindex top_builddir
  The relative path to the top-level of the current build tree.  In the
! actual top-level build directory, this is empty and should not be used.
  @end defvar
  
  @defvar abs_top_builddir
  @ovindex abs_top_builddir
! Absolute path of @code{top_builddir}.  In the actual top-level build
! directory, this value is not guaranteed to be useful (don't use it).
  @end defvar
  
  @defvar srcdir