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

to HACKING.  Updated recommended libtool version to be 1.3.4.

diff --git a/HACKING b/HACKING
index 3c26791..fda5899 100644 (file)
--- 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 ============================================
 

diff --git a/README b/README
index be9f01a..2a405a9 100644 (file)
--- a/README
+++ b/README
@@ -96,40 +96,6 @@ appears in your From: header, say foo@bar.com, send a mail note to
 guile-cvs-subscribe-foo=bar.com@sourceware.cygnus.com.
 
 
-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.3 --- 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.
-> 
-
-
 Obtaining Guile ======================================================
 
 The latest official Guile release is available via anonymous FTP from