summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorJim Blandy <jimb@red-bean.com>1999-09-19 01:01:25 +0000
committerJim Blandy <jimb@red-bean.com>1999-09-19 01:01:25 +0000
commitd4c83f63ff3db94246e9ee68715e86ceddea5005 (patch)
tree45d995033f453c239c83f33687dfcc803dab203d /HACKING
parent394a535ed069082c3ea76e46ba815a1541b5671c (diff)
*** empty log message ***
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING8
1 files changed, 8 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 2c6144e24..330782fd5 100644
--- 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