libguile/Makefile.am (snarfcppopts): Remove CFLAGS

[bpt/guile.git] / HACKING

diff --git a/HACKING b/HACKING
index f6d5185..b08f7c2 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -1,6 +1,6 @@
 -*-text-*-
 Guile Hacking Guide
-Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2008 Free software Foundation, Inc.
+Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2008, 2012 Free software Foundation, Inc.
 
    Permission is granted to anyone to make or distribute verbatim copies
    of this document as received, in any medium, provided that the
@@ -59,8 +59,9 @@ Automake --- a system for automatically generating Makefiles that
 
 libtool --- a system for managing the zillion hairy options needed
        on various systems to produce shared libraries.  Available in
-       "ftp://ftp.gnu.org/pub/gnu/libtool".  Version 1.5.26 (or
-       later) is needed for correct AIX support.
+       "ftp://ftp.gnu.org/pub/gnu/libtool".  Version 2.2 (or
+       later) is recommended (for correct AIX support, and correct
+       interaction with the Gnulib module for using libunistring).
 
 gettext --- a system for rigging a program so that it can output its
         messages in the local tongue.  Guile presently only exports
@@ -88,6 +89,10 @@ have been known to cause problems, and a short description of the problem.
 - autoreconf from autoconf prior to 2.59 will run gettextize, which
   will mess up the Guile tree.
 
+- libtool 1.5.26 does not know that it should remove the -R options
+  that the Gnulib libunistring and havelib modules generate (because
+  gcc doesn't actually support -R).
+
 - (add here.)
 
 
@@ -217,7 +222,7 @@ When deprecating a definition, always follow this procedure:
    manage without the deprecated definition.
 
 4. Add an entry that the definition has been deprecated in NEWS and
-   explain what do do instead.
+   explain what to do instead.
 
 5. In file TODO, there is a list of releases with reminders about what
    to do at each release.  Add a reminder about the removal of the
@@ -225,7 +230,7 @@ When deprecating a definition, always follow this procedure:
 
 - Write commit messages for functions written in C using the
 functions' C names, and write entries for functions written in Scheme
-using the functions' Scheme names.  For example, 
+using the functions' Scheme names.  For example,
 
   * foo.c: Moved scm_procedure_documentation from eval.c.
 
@@ -273,6 +278,12 @@ the list of years in the copyright notice at the top of the file.
 - When you get bug reports or patches from people, be sure to list
 them in THANKS.
 
+- Do not introduce trailing whitespace (and feel free to clean it up
+opportunistically, that is, if doing so is part of some other change).
+The goal is to reduce (and over time, eliminate) spurious diffs.
+
+For Emacs users:
+  (add-hook 'before-save-hook 'delete-trailing-whitespace)
 
 Naming conventions =================================================