From 9fb6bec17a0f67a9f9e044d62268096cf2200f78 Mon Sep 17 00:00:00 2001 From: Akim Demaille Date: Fri, 27 Jun 2003 11:47:26 +0000 Subject: [PATCH] * automake.texi: Use @node with a single argument. --- ChangeLog | 4 ++ automake.texi | 186 +++++++++++++++++++++++++------------------------- 2 files changed, 97 insertions(+), 93 deletions(-) diff --git a/ChangeLog b/ChangeLog index 031ea2f1..8d58e507 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2003-06-27 Akim Demaille + + * automake.texi: Use @node with a single argument. + 2003-06-27 Alexandre Duret-Lutz * m4/Makefile.am (dist_m4data_DATA): Add $(top_srcdir)/m4/amversion.m4. diff --git a/automake.texi b/automake.texi index 5190adeb..e42a4783 100644 --- a/automake.texi +++ b/automake.texi @@ -77,7 +77,7 @@ published by the Free Software Foundation raise funds for @syncodeindex cm cp @ifnottex -@node Top, Introduction, (dir), (dir) +@node Top @comment node-name, next, previous, up @top GNU Automake @@ -119,7 +119,7 @@ This edition documents version @value{VERSION}. @end ifnottex -@node Introduction, Generalities, Top, Top +@node Introduction @chapter Introduction Automake is a tool for automatically generating @file{Makefile.in}s from @@ -170,7 +170,7 @@ Mail suggestions and bug reports for Automake to @email{bug-automake@@gnu.org}. -@node Generalities, Examples, Introduction, Top +@node Generalities @chapter General ideas The following sections cover a few basic ideas that will help you @@ -186,7 +186,7 @@ understand how Automake works. @end menu -@node General Operation, Strictness, Generalities, Generalities +@node General Operation @section General Operation Automake works by reading a @file{Makefile.am} and generating a @@ -279,7 +279,7 @@ It is customary to make the first line of @file{Makefile.am} read: @c FIXME document customary ordering of Makefile.am here! -@node Strictness, Uniform, General Operation, Generalities +@node Strictness @section Strictness @cindex Non-GNU packages @@ -332,7 +332,7 @@ which are put into a ``Cygnus'' style tree (e.g., the GCC tree). For more information on this mode, see @ref{Cygnus}. -@node Uniform, Canonicalization, Strictness, Generalities +@node Uniform @section The Uniform Naming Scheme @cindex Uniform naming scheme @@ -462,7 +462,7 @@ are @samp{dist_}, @samp{nodist_}, and @samp{nobase_}. These prefixes are explained later (@pxref{Program and Library Variables}). -@node Canonicalization, User Variables, Uniform, Generalities +@node Canonicalization @section How derived variables are named @cindex canonicalizing Automake variables @@ -486,7 +486,7 @@ The strudel is an addition, to make the use of Autoconf substitutions in variable names less obfuscating. -@node User Variables, Auxiliary Programs, Canonicalization, Generalities +@node User Variables @section Variables reserved for the user @cindex variables, reserved for the user @@ -514,7 +514,7 @@ user variable's name. For instance, the shadow variable for @code{YFLAGS} is @code{AM_YFLAGS}. -@node Auxiliary Programs, , User Variables, Generalities +@node Auxiliary Programs @section Programs automake might require @cindex Programs, auxiliary @@ -583,7 +583,7 @@ directory in parallel. @end table -@node Examples, Invoking Automake, Generalities, Top +@node Examples @chapter Some example packages @menu @@ -593,7 +593,7 @@ directory in parallel. @end menu -@node Complete, Hello, Examples, Examples +@node Complete @section A simple example, start to finish @cindex Complete example @@ -659,7 +659,7 @@ Now you can run @code{automake --add-missing} to generate your you're done! -@node Hello, true, Complete, Examples +@node Hello @section A classic program @cindex Example, GNU Hello @@ -776,7 +776,7 @@ INCLUDES = -I../intl -DLOCALEDIR=\"$(localedir)\" @end example -@node true, , Hello, Examples +@node true @section Building true and false @cindex Example, false and true @@ -861,7 +861,7 @@ automake; they would be @file{false-true.o} and @file{true-true.o}. (The name of the object files rarely matters.) -@node Invoking Automake, configure, Examples, Top +@node Invoking Automake @chapter Creating a @file{Makefile.in} @cindex Multiple configure.in files @@ -1067,7 +1067,7 @@ for this reason. @end table -@node configure, Top level, Invoking Automake, Top +@node configure @chapter Scanning @file{configure.in} @cindex configure.in, scanning @@ -1096,7 +1096,7 @@ easier. These macros can automatically be put into your @end menu -@node Requirements, Optional, configure, configure +@node Requirements @section Configuration requirements @cindex Automake requirements @@ -1126,7 +1126,7 @@ These files are all removed by @code{make distclean}. @end table -@node Optional, Invoking aclocal, Requirements, configure +@node Optional @section Other things Automake recognizes @cindex Macros Automake recognizes @@ -1295,7 +1295,7 @@ opposed to macros installed in a system-wide directory, see @end table -@node Invoking aclocal, aclocal options, Optional, configure +@node Invoking aclocal @section Auto-generating aclocal.m4 @cindex Invoking aclocal @@ -1346,7 +1346,7 @@ using @file{acinclude.m4} in new packages (@pxref{Local Macros}). * Macro search path:: How aclocal finds .m4 files @end menu -@node aclocal options, Macro search path, Invoking aclocal, configure +@node aclocal options @section aclocal options @cindex aclocal, Options @@ -1395,7 +1395,7 @@ Print the names of the files it examines. Print the version number of Automake and exit. @end table -@node Macro search path, Macros, aclocal options, configure +@node Macro search path @section Macro search path @cindex Macro search path @@ -1538,7 +1538,7 @@ copy Automake on your account and want @command{aclocal} to look for macros installed at other places on the system. -@node Macros, Extending aclocal, Macro search path, configure +@node Macros @section Autoconf macros supplied with Automake Automake ships with several Autoconf macros that you can use from your @@ -1552,7 +1552,7 @@ Automake ships with several Autoconf macros that you can use from your @c consider generating the following subsections automatically from m4 files. -@node Public macros, Private macros, Macros, Macros +@node Public macros @subsection Public macros @table @code @@ -1707,7 +1707,7 @@ into @samp{LIBOBJS}. @end table -@node Private macros, , Public macros, Macros +@node Private macros @subsection Private macros The following macros are private macros you should not call directly. @@ -1744,7 +1744,7 @@ from @code{AM_INIT_AUTOMAKE}. @end table -@node Extending aclocal, Local Macros, Macros, configure +@node Extending aclocal @section Writing your own aclocal macros @cindex aclocal, extending @@ -1777,7 +1777,7 @@ Another situation where @command{aclocal} is commonly used is to manage macros which are used locally by the package, @ref{Local Macros}. -@node Local Macros, Future of aclocal, Extending aclocal, configure +@node Local Macros @section Handling Local Macros Feature tests offered by Autoconf do not cover all needs. People @@ -1846,7 +1846,7 @@ this requirement will hinder development. An easy solution is to copy such third-party macros in your local @file{m4/} directory so they get distributed. -@node Future of aclocal, , Local Macros, configure +@node Future of aclocal @section The Future of @command{aclocal} @cindex aclocal's scheduled death @@ -1888,7 +1888,7 @@ even likely you will not need the script anymore, and more to the point you will not call @command{aclocal} directly anymore. -@node Top level, Alternative, configure, Top +@node Top level @chapter The top-level @file{Makefile.am} @section Recursing subdirectories @@ -2065,7 +2065,7 @@ doesn't know the possible values of these variables. In this case @code{DIST_SUBDIRS} needs to be defined manually. -@node Alternative, Rebuilding, Top level, Top +@node Alternative @chapter An Alternative Approach to Subdirectories If you've ever read Peter Miller's excellent paper, @@ -2114,7 +2114,7 @@ either @samp{dist_} or @samp{nodist_} (@pxref{Dist}). For instance: nobase_dist_pkgdata_DATA = images/vortex.pgm @end example -@node Rebuilding, Programs, Alternative, Top +@node Rebuilding @chapter Rebuilding Makefiles Automake generates rules to automatically rebuild @file{Makefile}s, @@ -2132,7 +2132,7 @@ is only useful in the top-level @file{Makefile.am}. @vindex ACLOCAL_AMFLAGS -@node Programs, Other objects, Rebuilding, Top +@node Programs @chapter Building Programs and Libraries A large part of Automake's functionality is dedicated to making it easy @@ -2158,7 +2158,7 @@ to build programs and libraries. @end menu -@node A Program, A Library, Programs, Programs +@node A Program @section Building a program In order to build a program, you need to tell Automake which sources @@ -2175,7 +2175,7 @@ programs. Most of the comments about these also apply to libraries * Conditional Programs:: Building program conditionally @end menu -@node Program Sources, Linking, A Program, A Program +@node Program Sources @subsection Defining program sources @cindex PROGRAMS, bindir @@ -2243,7 +2243,7 @@ should not include the header file generated by @file{configure} in a and Lex}. -@node Linking, Conditional Sources, Program Sources, A Program +@node Linking @subsection Linking the program If you need to link against libraries that are not found by @@ -2311,7 +2311,7 @@ cause an invalid value for @samp{@var{prog}_DEPENDENCIES} to be generated. -@node Conditional Sources, Conditional Programs, Linking, A Program +@node Conditional Sources @subsection Conditional compilation of sources You can't put a configure substitution (e.g., @samp{@@FOO@@} or @@ -2397,7 +2397,7 @@ hello_SOURCES += hello-generic.c endif @end example -@node Conditional Programs, , Conditional Sources, A Program +@node Conditional Programs @subsection Conditional compilation of programs @cindex Conditional programs @cindex Programs, conditional @@ -2450,7 +2450,7 @@ endif @end example -@node A Library, A Shared Library, A Program, Programs +@node A Library @section Building a library @cindex _LIBRARIES primary, defined @@ -2512,7 +2512,7 @@ can override these two variables my setting them in your @file{configure.in}, or by defining a per-library @code{maude_AR} variable (@pxref{Program and Library Variables}). -@node A Shared Library, Program and Library Variables, A Library, Programs +@node A Shared Library @section Building a Shared Library @cindex Shared libraries, support for @@ -2583,7 +2583,7 @@ then you might wish to use a "nonstandard" name. In this case, put libtool, The Libtool Manual}, for more information. -@node Program and Library Variables, LIBOBJS, A Shared Library, Programs +@node Program and Library Variables @section Program and Library Variables Associated with each program are a collection of variables which can be @@ -2786,7 +2786,7 @@ This facility is rarely needed in practice, and we recommend avoiding it until you find it is required. @end table -@node LIBOBJS, Program variables, Program and Library Variables, Programs +@node LIBOBJS @section Special handling for LIBOBJS and ALLOCA @cindex @code{LIBOBJS}, special handling @@ -2803,7 +2803,7 @@ dependency-tracking scheme; see @xref{Dependencies}. @samp{_LDADD} or @samp{_LIBADD} variable. -@node Program variables, Yacc and Lex, LIBOBJS, Programs +@node Program variables @section Variables used when building a program Occasionally it is useful to know which @file{Makefile} variables @@ -2865,7 +2865,7 @@ and libraries to link in. @end vtable -@node Yacc and Lex, C++ Support, Program variables, Programs +@node Yacc and Lex @section Yacc and Lex support Automake has somewhat idiosyncratic support for Yacc and Lex. @@ -3005,7 +3005,7 @@ These defines work for @code{bison}, @code{byacc}, and traditional covered here, please report the new name so it can be added to the list. -@node C++ Support, Assembly Support, Yacc and Lex, Programs +@node C++ Support @section C++ Support @cindex C++ support @@ -3039,7 +3039,7 @@ The command used to actually link a C++ program. @end vtable -@node Assembly Support, Fortran 77 Support, C++ Support, Programs +@node Assembly Support @section Assembly Support Automake includes some support for assembly code. @@ -3060,7 +3060,7 @@ Only the suffixes @samp{.s} and @samp{.S} are recognized by @code{automake} as being files containing assembly code. -@node Fortran 77 Support, Java Support, Assembly Support, Programs +@node Fortran 77 Support @comment node-name, next, previous, up @section Fortran 77 Support @@ -3124,7 +3124,7 @@ These issues are covered in the following sections. @end menu -@node Preprocessing Fortran 77, Compiling Fortran 77 Files, Fortran 77 Support, Fortran 77 Support +@node Preprocessing Fortran 77 @comment node-name, next, previous, up @subsection Preprocessing Fortran 77 @@ -3148,7 +3148,7 @@ command used is as follows: @end table -@node Compiling Fortran 77 Files, Mixing Fortran 77 With C and C++, Preprocessing Fortran 77, Fortran 77 Support +@node Compiling Fortran 77 Files @comment node-name, next, previous, up @subsection Compiling Fortran 77 Files @@ -3170,7 +3170,7 @@ is as follows: @end table -@node Mixing Fortran 77 With C and C++, Fortran 77 and Autoconf, Compiling Fortran 77 Files, Fortran 77 Support +@node Mixing Fortran 77 With C and C++ @comment node-name, next, previous, up @subsection Mixing Fortran 77 With C and C++ @@ -3249,7 +3249,7 @@ Automake would have issued a warning. * How the Linker is Chosen:: @end menu -@node How the Linker is Chosen, , Mixing Fortran 77 With C and C++, Mixing Fortran 77 With C and C++ +@node How the Linker is Chosen @comment node-name, next, previous, up @subsubsection How the Linker is Chosen @@ -3302,7 +3302,7 @@ included by the C++ linker, then they must be manually added to an @end example -@node Fortran 77 and Autoconf, , Mixing Fortran 77 With C and C++, Fortran 77 Support +@node Fortran 77 and Autoconf @comment node-name, next, previous, up @subsection Fortran 77 and Autoconf @@ -3312,7 +3312,7 @@ Fortran 77 support was added to Autoconf 2.13, so you will want to use that version of Autoconf or later. -@node Java Support, Support for Other Languages, Fortran 77 Support, Programs +@node Java Support @comment node-name, next, previous, up @section Java Support @@ -3350,7 +3350,7 @@ using the @samp{--main=} option. The easiest way to do this is to use the @code{_LDFLAGS} variable for the program. -@node Support for Other Languages, ANSI, Java Support, Programs +@node Support for Other Languages @comment node-name, next, previous, up @section Support for Other Languages @@ -3363,7 +3363,7 @@ Some limited support for adding your own languages is available via the suffix rule handling; see @ref{Suffixes}. -@node ANSI, Dependencies, Support for Other Languages, Programs +@node ANSI @section Automatic de-ANSI-fication @cindex de-ANSI-fication, defined @@ -3431,7 +3431,7 @@ in @code{LIBOBJS}. This is no longer true today. Starting with version @code{LTLIBOBJS}. (@pxref{AC_LIBOBJ vs LIBOBJS, , @code{AC_LIBOBJ} vs. @code{LIBOBJS}, autoconf, The Autoconf Manual}) -@node Dependencies, EXEEXT, ANSI, Programs +@node Dependencies @section Automatic dependency tracking As a developer it is often painful to continually update the @@ -3478,7 +3478,7 @@ tracking by configuring with @code{--disable-dependency-tracking}. @cindex Dependency tracking, disabling -@node EXEEXT, , Dependencies, Programs +@node EXEEXT @section Support for executable extensions @cindex Executable extension @@ -3538,7 +3538,7 @@ automake-generated target of the form @code{foo$(EXEEXT)}. Without the @code{no-exeext} option, this use will give an error. -@node Other objects, Other GNU Tools, Programs, Top +@node Other objects @chapter Other Derived Objects Automake can handle derived objects which are not C programs. Sometimes @@ -3554,7 +3554,7 @@ distribution. @end menu -@node Scripts, Headers, Other objects, Other objects +@node Scripts @section Executable Scripts @cindex _SCRIPTS primary, defined @@ -3599,7 +3599,7 @@ Scripts that need not being installed can be listed in @code{make check} should go in @code{check_SCRIPTS}. -@node Headers, Data, Scripts, Other objects +@node Headers @section Header files @cindex _HEADERS primary, defined @@ -3633,7 +3633,7 @@ Headers can be installed in @code{includedir}, @code{oldincludedir}, or @code{pkgincludedir}. -@node Data, Sources, Headers, Other objects +@node Data @section Architecture-independent data files @cindex _DATA primary, defined @@ -3665,7 +3665,7 @@ dist_pkgdata_DATA = clean-kr.am clean.am @dots{} @end example -@node Sources, , Data, Other objects +@node Sources @section Built sources Because Automake's automatic dependency tracking works as a side-effect @@ -3727,7 +3727,7 @@ on a toy example. * Built sources example:: Several ways to handle built sources. @end menu -@node Built sources example, , Sources, Sources +@node Built sources example @subsection Built sources example Suppose that @file{foo.c} includes @file{bindir.h}, which is @@ -3915,7 +3915,7 @@ Building files from @file{./configure} is not always possible, neither is converting @file{.h} files into @file{.c} files. -@node Other GNU Tools, Documentation, Other objects, Top +@node Other GNU Tools @chapter Other GNU Tools Since Automake is primarily intended to generate @file{Makefile.in}s for @@ -3930,7 +3930,7 @@ use in GNU programs, it tries hard to interoperate with other GNU tools. @end menu -@node Emacs Lisp, gettext, Other GNU Tools, Other GNU Tools +@node Emacs Lisp @section Emacs Lisp @cindex _LISP primary, defined @@ -3960,7 +3960,7 @@ that you byte-compile your Emacs Lisp sources. It is probably better for sites with strange setups to cope for themselves than to make the installation less nice for everybody else. -@node gettext, Libtool, Emacs Lisp, Other GNU Tools +@node gettext @section Gettext @cindex GNU Gettext support @@ -3984,7 +3984,7 @@ Lisp sources are not distributed by default. You can prefix the @code{dist_noinst_LISP}, to indicate that these files should be distributed. -@node Libtool, Java, gettext, Other GNU Tools +@node Libtool @section Libtool Automake provides support for GNU Libtool (@pxref{Top, , Introduction, @@ -3992,7 +3992,7 @@ libtool, The Libtool Manual}) with the @samp{LTLIBRARIES} primary. @xref{A Shared Library}. -@node Java, Python, Libtool, Other GNU Tools +@node Java @section Java @cindex _JAVA primary, defined @@ -4044,7 +4044,7 @@ This variable is an @code{sh} expression which is used to set the @end vtable -@node Python, , Java, Other GNU Tools +@node Python @section Python @cindex _PYTHON primary, defined @@ -4130,7 +4130,7 @@ manual has a section with more details on this topic Variables, autoconf, The Autoconf Manual}). -@node Documentation, Install, Other GNU Tools, Top +@node Documentation @chapter Building documentation Currently Automake provides support for Texinfo and man pages. @@ -4141,7 +4141,7 @@ Currently Automake provides support for Texinfo and man pages. @end menu -@node Texinfo, Man pages, Documentation, Documentation +@node Texinfo @section Texinfo @cindex _TEXINFOS primary, defined @@ -4271,7 +4271,7 @@ use this. By default, info pages are installed by @samp{make install}. This can be prevented via the @code{no-installinfo} option. -@node Man pages, , Texinfo, Documentation +@node Man pages @section Man pages @cindex _MANS primary, defined @@ -4341,7 +4341,7 @@ The @samp{nobase_} prefix is meaningless for man pages and is disallowed. -@node Install, Clean, Documentation, Top +@node Install @chapter What Gets Installed @cindex Installation support @@ -4469,7 +4469,7 @@ Note that @code{uninstall} is not meant as a replacement for a real packaging tool. -@node Clean, Dist, Install, Top +@node Clean @chapter What Gets Cleaned @cindex make clean support @@ -4513,7 +4513,7 @@ We recommend that you follow this same set of heuristics in your @file{Makefile.am}. -@node Dist, Tests, Clean, Top +@node Dist @chapter What Goes in a Distribution @section Basics of distribution @@ -4762,7 +4762,7 @@ archives in all the enabled formats, @ref{Options}. By default, only the @code{dist-gzip} target is hooked to @code{dist}. -@node Tests, Options, Dist, Top +@node Tests @chapter Support for test suites @cindex Test suites @@ -4863,7 +4863,7 @@ any tests after the package has been installed. You can add tests to this by writing an @code{installcheck-local} target. -@node Options, Miscellaneous, Tests, Top +@node Options @chapter Changing Automake's Behavior Various features of Automake can be controlled by options in the @@ -5047,7 +5047,7 @@ the @code{AM_INIT_AUTOMAKE} macro in @file{configure.in}. @xref{Macros}. -@node Miscellaneous, Include, Options, Top +@node Miscellaneous @chapter Miscellaneous Rules There are a few rules and variables that didn't fit anywhere else. @@ -5059,7 +5059,7 @@ There are a few rules and variables that didn't fit anywhere else. @end menu -@node Tags, Suffixes, Miscellaneous, Miscellaneous +@node Tags @section Interfacing to @code{etags} @cindex TAGS support @@ -5118,7 +5118,7 @@ variable @code{GTAGS_ARGS} holds arguments which are passed to @vindex GTAGS_ARGS -@node Suffixes, Multilibs, Tags, Miscellaneous +@node Suffixes @section Handling new file extensions @cindex Adding new SUFFIXES @@ -5169,7 +5169,7 @@ Automake generate the suffix list for @code{.SUFFIXES}. Any given @code{SUFFIXES} go at the start of the generated suffixes list, followed by Automake generated suffixes not already in the list. -@node Multilibs, , Suffixes, Miscellaneous +@node Multilibs @section Support for Multilibs Automake has support for an obscure feature called multilibs. A @@ -5183,7 +5183,7 @@ The multilib support is still experimental. Only use it if you are familiar with multilibs and can debug problems you might encounter. -@node Include, Conditionals, Miscellaneous, Top +@node Include @chapter Include @cmindex include @@ -5213,7 +5213,7 @@ condition applies to the entire contents of that fragment. Makefile fragments included this way are always distributed because there are needed to rebuild @file{Makefile.in}. -@node Conditionals, Gnits, Include, Top +@node Conditionals @chapter Conditionals @cindex Conditionals @@ -5306,7 +5306,7 @@ in the @file{Makefile}. Automake conditionals will work with any make program. -@node Gnits, Cygnus, Conditionals, Top +@node Gnits @chapter The effect of @code{--gnu} and @code{--gnits} @cindex --gnu, required files @@ -5368,7 +5368,7 @@ The file @file{THANKS} is required. @end itemize -@node Cygnus, Extending, Gnits, Top +@node Cygnus @chapter The effect of @code{--cygnus} @cindex Cygnus strictness @@ -5426,7 +5426,7 @@ more standards compliant). At that time the special Cygnus mode will be removed. -@node Extending, Distributing, Cygnus, Top +@node Extending @chapter When Automake Isn't Enough Automake's implicit copying semantics means that many problems can be @@ -5541,7 +5541,7 @@ destination directory in order to create relative links. @c FIXME should include discussion of variables you can use in these @c rules -@node Distributing, API versioning, Extending, Top +@node Distributing @chapter Distributing @file{Makefile.in}s Automake places no restrictions on the distribution of the resulting @@ -5555,7 +5555,7 @@ have a special exception allowing you to distribute them with your package, regardless of the licensing you choose. -@node API versioning, FAQ, Distributing, Top +@node API versioning @chapter Automake API versioning New Automake releases usually include bug fixes and new features. @@ -5620,7 +5620,7 @@ If it turns out you need to use such a undocumented feature, contact @email{automake@@gnu.org} and try to get it documented and exercised by the test-suite. -@node FAQ, Macro and Variable Index, API versioning, Top +@node FAQ @chapter Frequently Asked Questions about Automake This chapter covers some questions that often come up on the mailing @@ -5634,7 +5634,7 @@ lists. * renamed objects:: Why are object files sometimes renamed? @end menu -@node CVS, maintainer-mode, FAQ, FAQ +@node CVS @section CVS and generated files @subsection Background: distributed generated files @@ -5796,7 +5796,7 @@ concerns about version mismatch between developers' tools. The Gettext manual has a section about this, see @ref{CVS Issues, CVS Issues, Integrating with CVS, gettext, GNU gettext tools}. -@node maintainer-mode, wildcards, CVS, FAQ +@node maintainer-mode @section @command{missing} and @code{AM_MAINTAINER_MODE} @subsection @command{missing} @@ -5875,7 +5875,7 @@ and because @command{missing} isn't enough if you have the wrong version of the tools. -@node wildcards, distcleancheck, maintainer-mode, FAQ +@node wildcards @section Why doesn't Automake support wildcards? @cindex wildcards @@ -5952,7 +5952,7 @@ variables as far Automake is concerned. You can get warnings about @code{$(wildcard ...}) constructs using the @code{-Wportability} flag. -@node distcleancheck, renamed objects, wildcards, FAQ +@node distcleancheck @section Files left in build directory after distclean @cindex distclean, diagnostic @cindex dependencies and distributed files @@ -6099,7 +6099,7 @@ Make sure you do understand the reason why @code{make distcheck} complains before you do this. @code{distcleancheck_listfiles} is a way to @emph{hide} errors, not to fix them. You can always do better. -@node renamed objects, , distcleancheck, FAQ +@node renamed objects @section Why are object files sometimes renamed? This happens when per-target compilation flags are used. Object @@ -6142,14 +6142,14 @@ Note that the renaming of objects is also affected by the @code{_SHORTNAME} variable (@pxref{Program and Library Variables}). @page -@node Macro and Variable Index, General Index, FAQ, Top +@node Macro and Variable Index @unnumbered Macro and Variable Index @printindex vr @page -@node General Index, , Macro and Variable Index, Top +@node General Index @unnumbered General Index @printindex cp -- 2.43.5