* README-hacking: Describe how to build with LZMA.

diff --git a/ChangeLog b/ChangeLog
index 49e517491d1728f198bd8591a20ebc93d0971cef..51515d1ea6c8882fd22cc744034e3db6e2f7c0ff 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2007-10-22  Paul Eggert  <eggert@cs.ucla.edu>
+
+       * README-hacking: Describe how to build with LZMA.
+
 2007-10-22  Jim Meyering  <meyering@redhat.com>
 
        Remove git-version-gen's first parameter.

diff --git a/README-hacking b/README-hacking
index 3539d73782ddf25f9c7c9386b237da6f714dad1f..77464bd7d82e8e69b2c39292aeab17688b40b69d 100644 (file)
--- a/README-hacking
+++ b/README-hacking
@@ -27,6 +27,29 @@ Valgrind supports your architecture.
 Only building the initial full source tree will be a bit painful.
 Later, a plain `git-pull && make' should be sufficient.
 
+* LZMA
+
+The coreutils build procedure can build distribution tarballs with the
+LZMA compression scheme.  This feature is so new that it is not
+supported by the latest version of Automake.  If you don't care about
+building LZMA tarballs, you can manually remove the string "dist-lzma"
+from configure.ac before bootstrapping.
+
+If you do want to build LZMA tarballs, you'll need to make sure you
+have the latest stable version of the LZMA SDK
+<http://www.7-zip.org/sdk.html>.  Also, you'll need a version of
+Automake that supports the dist-lzma feature, which was added to
+Automake on 2007-10-09 but is not yet available in a stable Automake
+version.  So until Automake 1.11 comes out, you'll need to get the
+bleeding-edge Automake version with a command like this:
+
+       $ cvs -d sources.redhat.com:/cvs/automake co automake
+       $ ./bootstrap
+       $ ./configure
+       $ make install
+
+and build and install that version.
+
 * First GIT checkout
 
 Obviously, if you are reading these notes, you did manage to check out