From d4c83f63ff3db94246e9ee68715e86ceddea5005 Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Sun, 19 Sep 1999 01:01:25 +0000 Subject: [PATCH] *** empty log message *** --- HACKING | 8 ++++++++ RELEASE | 4 ++++ 2 files changed, 12 insertions(+) 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 diff --git a/RELEASE b/RELEASE index 60eeaf443..7b76132ba 100644 --- a/RELEASE +++ b/RELEASE @@ -49,6 +49,10 @@ Julian Satchell : dec-mips-ultrix +Perry Metzger + + NetBSD + Release Checklists ===================================================