* README, HACKING: Moved "Hacking it yourself" section from README

to HACKING.  Updated recommended libtool version to be 1.3.4.

1 files changed, 33 insertions, 1 deletions

diff --git a/HACKING b/HACKING
index 3c26791c0..fda589965 100644
--- a/HACKING
+++ b/HACKING
@@ -1,4 +1,36 @@
-Here are some guidelines for members of the Guile developers team.
+Hacking It Yourself ==================================================
+
+As distributed, Guile needs only an ANSI C compiler and a Unix system
+to compile.  However, Guile's makefiles, configuration scripts, and a
+few other files are automatically generated, not written by hand.  If
+you want to make changes to the system (which we encourage!) you will
+find it helpful to have the tools we use to develop Guile.  They
+are the following:
+
+Autoconf 2.13 --- 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 --- 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
+	`guile.m4' from the top directory of the Guile core disty to
+	`/usr/local/share/aclocal.
+
+libtool 1.3.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"
+
+You are lost in a little maze of automatically generated files, all
+different.
+> 
+
 
 Contributing Your Changes ============================================