Update XZ Utils to 5.0.4 (third_party)

INSTALL

 
 XZ Utils Installation
 =====================
 
     0. Preface
     1. Supported platforms
        1.1. Compilers
        1.2. Platform-specific notes
-            1.2.1. IRIX
-            1.2.2. MINIX 3
-            1.2.3. OpenVMS
-            1.2.4. Solaris, OpenSolaris, and derivatives
-            1.2.5. Tru64
-            1.2.6. Windows
-            1.2.7. DOS
+            1.2.1. AIX
+            1.2.2. IRIX
+            1.2.3. MINIX 3
+            1.2.4. OpenVMS
+            1.2.5. Solaris, OpenSolaris, and derivatives
+            1.2.6. Tru64
+            1.2.7. Windows
+            1.2.8. DOS
        1.3. Adding support for new platforms
     2. configure options
        2.1. Static vs. dynamic linking of liblzma
        2.2. Optimizing xzdec and lzmadec
     3. xzgrep and other scripts
        3.1. Dependencies
        3.2. PATH
     4. Troubleshooting
        4.1. "No C99 compiler was found."
        4.2. "No POSIX conforming shell (sh) was found."
@@ skipping 30 matching lines @@
     C99 features used in XZ Utils source code, thus GCC 2 won't compile
     XZ Utils.
 
     XZ Utils takes advantage of some GNU C extensions when building
     with GCC. Because these extensions are used only when building
     with GCC, it should be possible to use any C99 compiler.
 
 
 1.2. Platform-specific notes
 
-1.2.1. IRIX
+1.2.1. AIX
+
+    If you use IBM XL C compiler, pass CC=xlc_r to configure. If
+    you use CC=xlc instead, you must disable threading support
+    with --disable-threads (usually not recommended).
+
+
+1.2.2. IRIX
 
     MIPSpro 7.4.4m has been reported to produce broken code if using
     the -O2 optimization flag ("make check" fails). Using -O1 should
     work.
 
     A problem has been reported when using shared liblzma. Passing
     --disable-shared to configure works around this. Alternatively,
     putting "-64" to CFLAGS to build a 64-bit version might help too.
 
 
-1.2.2. MINIX 3
+1.2.3. MINIX 3
 
     The default install of MINIX 3 includes Amsterdam Compiler Kit (ACK),
     which doesn't support C99. Install GCC to compile XZ Utils.
 
-    MINIX 3.1.8 (and possibly some other versions too) has bugs in
-    /usr/include/stdint.h, which has to be patched before XZ Utils
-    can be compiled correctly. See
+    MINIX 3.1.8 and older have bugs in /usr/include/stdint.h, which has
+    to be patched before XZ Utils can be compiled correctly. See
     <http://gforge.cs.vu.nl/gf/project/minix/tracker/?action=TrackerItemEdit&tracker_item_id=537>.
 
+    MINIX 3.2.0 and later use a different libc and aren't affected by
+    the above bug.
+
     XZ Utils doesn't have code to detect the amount of physical RAM and
     number of CPU cores on MINIX 3.
 
     See section 4.4 in this file about symbol visibility warnings (you
     may want to pass gl_cv_cc_visibility=no to configure).
 
 
-1.2.3. OpenVMS
+1.2.4. OpenVMS
 
     XZ Utils can be built for OpenVMS, but the build system files
     are not included in the XZ Utils source package. The required
     OpenVMS-specific files are maintained by Jouk Jansen and can be
     downloaded here:
 
         http://nchrem.tnw.tudelft.nl/openvms/software2.html#xzutils
 
 
-1.2.4. Solaris, OpenSolaris, and derivatives
+1.2.5. Solaris, OpenSolaris, and derivatives
 
     The following linker error has been reported on some x86 systems:
 
         ld: fatal: relocation error: R_386_GOTOFF: ...
 
     This can be worked around by passing gl_cv_cc_visibility=no
     as an argument to the configure script.
 
 
-1.2.5. Tru64
+1.2.6. Tru64
 
     If you try to use the native C compiler on Tru64 (passing CC=cc to
     configure), you may need the workaround mention in section 4.1 in
     this file (pass also ac_cv_prog_cc_c99= to configure).
 
 
-1.2.6. Windows
+1.2.7. Windows
 
     Building XZ Utils on Windows is supported under MinGW + MSYS,
     MinGW-w64 + MSYS, and Cygwin. There is windows/build.bash to
     ease packaging XZ Utils with MinGW(-w64) + MSYS into a
     redistributable .zip or .7z file. See windows/INSTALL-Windows.txt
     for more information.
 
     It might be possible to build liblzma with a non-GNU toolchain too,
     but that will probably require writing a separate makefile. Building
     the command line tools with non-GNU toolchains will be harder than
     building only liblzma.
 
     Even if liblzma is built with MinGW, the resulting DLL or static
     library can be used by other compilers and linkers, including MSVC.
     Thus, it shouldn't be a problem to use MinGW to build liblzma even
     if you cannot use MinGW to build the rest of your project. See
     windows/README-Windows.txt for details.
 
 
-1.2.7. DOS
+1.2.8. DOS
 
     There is an experimental Makefile in the "dos" directory to build
     XZ Utils on DOS using DJGPP. Support for long file names (LFN) is
     needed. See dos/README for more information.
 
     GNU Autotools based build hasn't been tried on DOS. If you try, I
     would like to hear if it worked.
 
 
 1.3. Adding support for new platforms
@@ skipping 294 matching lines @@
 
     On some systems where symbol visibility isn't supported, GCC may
     still accept the visibility options and attributes, which will make
     configure think that visibility is supported. This will result in
     many compiler warnings. You can avoid the warnings by forcing the
     visibility support off by passing gl_cv_cc_visibility=no as an
     argument to the configure script. This has no effect on the
     resulting binaries, but fewer warnings looks nicer and may allow
     using --enable-werror.