Added blurb about libltdl support.

[bpt/guile.git] / HACKING

diff --git a/HACKING b/HACKING
index 2c6144e..3c26791 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -57,6 +57,14 @@ general rule is that you should be able to check out a working
 directory of Guile from CVS, and then type "configure" and "make",
 without running any other tools.
 
+- (Automake 1.4 only) Be sure to run automake at the top of the tree
+with no arguments.  Do not use `automake Makefile' to regenerate
+specific Makefile.in files, and do not trust the Makefile rules to
+rebuild them when they are out of date.  Automake 1.4 will add
+extraneous rules to the top-level Makefile if you specify specific
+Makefiles to rebuild on the command line.  Running the command
+`autoreconf --force' should take care of everything correctly.
+
 - Make sure your changes compile and work, at least on your own
 machine, before checking them into the main branch of the Guile
 repository.  If you really need to check in untested changes, make a
@@ -78,14 +86,16 @@ make-stds.texi.
 - The Guile tree should compile without warnings under the following
 GCC switches, which are the default in the current configure script:
     -O2 -Wall -Wpointer-arith -Wmissing-prototypes
-The only exceptions are the warnings about variables being clobbered
-by longjmp/vfork in eval.c.  (Tho' if you can figure out how to get
-rid of those, too, I'd be happy.)
+The only warnings which can be tolerated are those about variables
+being clobbered by longjmp/vfork in eval.c.  The variables in question
+are critical to the interpreter's performance; as far as I can tell,
+it is difficult/annoying to avoid these warnings without slowing the
+system down substantially.  (If you can figure out a good fix, I'd be happy to see it.)
 
 Note that the warnings generated vary from one version of GCC to the
 next, and from one architecture to the next (apparently).  To provide
 a concrete common standard, Guile should compile without warnings from
-GCC 2.7.2.3 in a Red Hat 5.0 i386 Linux machine.  Furthermore, each
+GCC 2.7.2.3 in a Red Hat 5.2 i386 Linux machine.  Furthermore, each
 developer should pursue any additional warnings noted by on their
 compiler.  This means that people using more stringent compilers will
 have more work to do, and assures that everyone won't switch to the