* HACKING: Modified the Hacking It Yourself section. Removed the

version numbers from the tools.

ChangeLog

@@ -1,3 +1,8 @@
+2001-11-22  Gary Houston  <ghouston@arglist.com>
+
+	* HACKING: Modified the Hacking It Yourself section.  Removed the
+	version numbers from the tools.
+
 2001-11-21  Gary Houston  <ghouston@arglist.com>
 
 	* HACKING: Removed reference to no longer practiced * in ChangeLog

HACKING

@@ -22,8 +22,8 @@ You can hack whatever you want, thank GNU.
 
 However, to see what others have indicated as their interest (and avoid
 potential wasteful duplication of effort), see file TODO.  Note that
-the version you find may be out of date; a CVS checkout is recommended
+the version you find may be out of date; a CVS checkout is recommended:
-(see also file SNAPSHOTS).
+see below for details (see also file SNAPSHOTS).
 
 It's also a good idea to join the guile-devel@gnu.org mailing list.
 See http://www.gnu.org/software/guile/mail/mail.html for more info.
@@ -31,43 +31,42 @@ See http://www.gnu.org/software/guile/mail/mail.html for more info.
 
 Hacking It Yourself ==================================================
 
-As distributed, Guile needs only an ANSI C compiler and a Unix system
+When Guile is obtained from CVS, a few extra steps must be taken
-to compile.  However, Guile's makefiles, configuration scripts, and a
+before the usual configure, make, make install.  You will need to have
-few other files are automatically generated, not written by hand.  If
+up-to-date versions of the tools listed below, correctly installed.
-you want to make changes to the system (which we encourage!) you will
+i.e., they must be found in the current PATH and not shadowed or
-find it helpful to have the tools we use to develop Guile.  They
+otherwise broken by files left behind from older versions.
-are the following:
 
-Autoconf 2.50 --- a system for automatically generating `configure'
+"up-to-date" means the latest released versions at the time that Guile
+was obtained from CVS.  Sometimes older versions will work.
+
+Then you must run the autogen.sh script, as described below.
+
+In case of problems, it may be worth getting a fresh copy of Guile
+from CVS: synchronisation problems have been known to occur
+occasionally.
+
+Autoconf --- a system for automatically generating `configure'
 	scripts from templates which list the non-portable features a
 	program would like to use.  Available in
 	"ftp://ftp.gnu.org/pub/gnu/autoconf"
 
-Automake 1.4-p4 --- a system for automatically generating Makefiles that
+Automake --- a system for automatically generating Makefiles that
 	conform to the (rather Byzantine) GNU coding standards.  The
 	nice thing is that it takes care of hairy targets like 'make
 	dist' and 'make distclean', and automatically generates
 	Makefile dependencies.  Automake is available in
 	"ftp://ftp.gnu.org/pub/gnu/automake"
 
-	Before using automake, you may need to copy `threads.m4' and
+libtool --- a system for managing the zillion hairy options needed
-	`guile.m4' from the top directory of the Guile core disty to
-	`/usr/local/share/aclocal'.
-
-libtool 1.4 --- 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"
 
-	To avoid reported tricky errors during the Guile build: After
+flex --- a scanner generator.  It's probably not essential to have the
-	unpacking the libtool distribution, use autoconf (2.50) to
+        latest version.
-	regenerate its ./configure script.  Then build and install as
-	usual.
 
-flex 2.5.4 (or newer) --- a scanner generator.  earlier versions will
+One false move and you will be lost in a little maze of automatically
-        most probably work too.
+generated files, all different.
-
-You are lost in a little maze of automatically generated files, all
-different.
 
 
 Sample GDB Initialization File=========================================