gnustandards ChangeLog make-stds.texi

[Karl Berry]

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       08/04/08 12:57:49

Modified files:
        .              : ChangeLog make-stds.texi 

Log message:
        portability notes checkin

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.70&r2=1.71
http://cvs.savannah.gnu.org/viewcvs/gnustandards/make-stds.texi?cvsroot=gnustandards&r1=1.51&r2=1.52

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -b -r1.70 -r1.71
--- ChangeLog   30 Mar 2008 22:01:02 -0000      1.70
+++ ChangeLog   8 Apr 2008 12:57:49 -0000       1.71
@@ -1,14 +1,14 @@
-2008-03-30  Ralf Wildenhues  <address@hidden>
-
-       * standards.texi: Fix links to config and gnulib repos, add some
-       `@/' to url's.
-
-2008-03-24  Ralf Wildenhues  <address@hidden>
+2008-04-08  Ralf Wildenhues  <address@hidden>
        and Karl Berry  <address@hidden>
 
        * make-stds.texi (General Conventions for Makefiles): more notes
        on portability.
 
+2008-03-30  Ralf Wildenhues  <address@hidden>
+
+       * standards.texi: Fix links to config and gnulib repos, add some
+       `@/' to url's.
+
 2008-03-21  Karl Berry  <address@hidden>
 
        * maintain.texi (Copyright Notices): missing "of".

Index: make-stds.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/make-stds.texi,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- make-stds.texi      14 Feb 2008 17:03:48 -0000      1.51
+++ make-stds.texi      8 Apr 2008 12:57:49 -0000       1.52
@@ -33,7 +33,10 @@
 @end iftex
 describes conventions for writing the Makefiles for GNU programs.
 Using Automake will help you write a Makefile that follows these
-conventions.
+conventions.  For more information on portable Makefiles, see
address@hidden and @ref{Portable Make, Portable Make Programming,, autoconf,
+Autoconf}.
+
 
 @menu
 * Makefile Basics::             General conventions for Makefiles.
@@ -144,8 +147,10 @@
 @section Utilities in Makefiles
 
 Write the Makefile commands (and any shell scripts, such as
address@hidden) to run in @code{sh}, not in @code{csh}.  Don't use any
-special features of @code{ksh} or @code{bash}.
address@hidden) to run under @code{sh} (both the traditional Bourne
+shell and the @sc{posix} shell), not @code{csh}.  Don't use any
+special features of @code{ksh} or @code{bash}, or @sc{posix} features
+not widely supported in traditional Bourne @code{sh}.
 
 The @code{configure} script and the Makefile rules for building and
 installation should not use any utilities directly except these:
@@ -162,12 +167,16 @@
 Compression programs such as @code{gzip} can be used in the
 @code{dist} rule.
 
-Stick to the generally supported options for these programs.  For
-example, don't use @samp{mkdir -p}, convenient as it may be, because
-most systems don't support it.
+Generally, stick to the widely-supported (usually
address@hidden) options and features of these programs.  For
+example, don't use @samp{mkdir -p}, convenient as it may be, because a
+few systems don't support it at all and with others, it is not safe
+for parallel execution.  For a list of known incompatibilities, see
address@hidden Shell, Portable Shell Programming,, autoconf, Autoconf}.
+
 
 It is a good idea to avoid creating symbolic links in makefiles, since a
-few systems don't support them.
+few file systems don't support them.
 
 The Makefile rules for building and installation can also use compilers
 and related programs, but should do so via @code{make} variables so that the