From 0569949c6120b3609a23b3b89f3b3f15f643f7b1 Mon Sep 17 00:00:00 2001 From: Eric Blake Date: Wed, 8 Sep 2010 09:11:31 -0600 Subject: [PATCH] docs: link to GNU Coding Standards in intro * doc/autoconf.texi (Introduction): Actually link to the standards. Make other references consistent. Signed-off-by: Eric Blake --- ChangeLog | 4 ++++ doc/autoconf.texi | 9 +++++---- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index 77d513cd..c874eabe 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2010-09-08 Eric Blake + docs: link to GNU Coding Standards in intro + * doc/autoconf.texi (Introduction): Actually link to the + standards. Make other references consistent. + docs: mention traditional awk limitation * doc/autoconf.texi (Limitations of Usual Tools) : Mention that traditional awk lacks ENVIRON. Add reference to awk manual. diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 24c6e149..99054c59 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -728,7 +728,8 @@ about difficulties in writing Autoconf input, and not in the behavior of the resulting @file{configure}. Even packages that don't use Autoconf will generally provide a @file{configure} script, and the most common complaint about these alternative home-grown scripts is that they fail -to meet one or more of the GNU Coding Standards that users +to meet one or more of the GNU Coding Standars (@pxref{Configuration, , , +standards, The GNU Coding Standards}) that users have come to expect from Autoconf-generated @file{configure} scripts. The Metaconfig package is similar in purpose to Autoconf, but the @@ -14671,7 +14672,7 @@ However, these ancient systems are no longer of practical concern. The set of external programs you should run in a @command{configure} script is fairly small. @xref{Utilities in Makefiles, , Utilities in -Makefiles, standards, GNU Coding Standards}, for the list. This +Makefiles, standards, The GNU Coding Standards}, for the list. This restriction allows users to start out with a fairly small set of programs and build the rest, avoiding too many interdependencies between packages. @@ -20121,7 +20122,7 @@ and the rest of section assumes at least C89, the first C standard. Program portability is a huge topic, and this section can only briefly introduce common pitfalls. @xref{System Portability, , Portability -between System Types, standards, GNU Coding Standards}, for +between System Types, standards, The GNU Coding Standards}, for more information. @menu @@ -21393,7 +21394,7 @@ by an environment variable. The programs should examine that file at runtime, rather than at compile time. Runtime configuration is more convenient for users and makes the configuration process simpler than getting the information while configuring. @xref{Directory Variables, , -Variables for Installation Directories, standards, GNU Coding +Variables for Installation Directories, standards, The GNU Coding Standards}, for more information on where to put data files. @node Transforming Names -- 2.11.4.GIT