[Top][All Lists]

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

gnustandards ChangeLog make-stds.texi

From: Karl Berry
Subject: gnustandards ChangeLog make-stds.texi
Date: Tue, 23 Nov 2010 00:21:22 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       10/11/23 00:21:22

Modified files:
        .              : ChangeLog make-stds.texi 

Log message:
        additional info about stripping executables, from Ralf W


Index: ChangeLog
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.128
retrieving revision 1.129
diff -u -b -r1.128 -r1.129
--- ChangeLog   23 Nov 2010 00:17:17 -0000      1.128
+++ ChangeLog   23 Nov 2010 00:21:22 -0000      1.129
@@ -1,3 +1,9 @@
+2010-11-22  Ralf Wildenhues  <address@hidden>
+       * doc/make-stds.texi (Standard Targets): Additional information
+       about stripping executables.
+       Suggested by Mark T. Eriksen <halfcountplus at intergate dot com>.
 2010-11-22  Karl Berry  <address@hidden>
        * maintain.texi (Donations): mention FSF, software

Index: make-stds.texi
RCS file: /sources/gnustandards/gnustandards/make-stds.texi,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
--- make-stds.texi      25 Aug 2010 00:07:21 -0000      1.61
+++ make-stds.texi      23 Nov 2010 00:21:22 -0000      1.62
@@ -724,8 +724,11 @@
 simple test to verify that a program is properly installed, this target
 should run that test.
-Do not strip executables when installing them.  Devil-may-care users can
-use the @code{install-strip} target to do that.
+Do not strip executables when installing them.  This helps eventual
+debugging that may be needed later, and nowadays disk space is cheap
+and dynamic loaders typically ensure debug sections are not loaded during
+normal execution.  Users that need stripped binaries may invoke the
address@hidden target to do that.
 If possible, write the @code{install} target rule so that it does not
 modify anything in the directory where the program was built, provided

reply via email to

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