| blob | 624a10794802b69e751ccc0617d9a2004122e8af |
2 XZ Utils Installation
3 =====================
5 0. Preface
6 1. Supported platforms
7 1.1. Compilers
8 1.2. Platform-specific notes
9 1.2.1. AIX
10 1.2.2. IRIX
11 1.2.3. MINIX 3
12 1.2.4. OpenVMS
13 1.2.5. Solaris, OpenSolaris, and derivatives
14 1.2.6. Tru64
15 1.2.7. Windows
16 1.2.8. DOS
17 1.2.9. z/OS
18 1.3. Adding support for new platforms
19 2. configure options
20 2.1. Static vs. dynamic linking of liblzma
21 2.2. Optimizing xzdec and lzmadec
22 3. xzgrep and other scripts
23 3.1. Dependencies
24 3.2. PATH
25 4. Tests
26 4.1 Testing in parallel
27 4.2 Cross compiling
28 5. Troubleshooting
29 5.1. "No C99 compiler was found."
30 5.2. "No POSIX conforming shell (sh) was found."
31 5.3. configure works but build fails at crc32_x86.S
32 5.4. Lots of warnings about symbol visibility
33 5.5. "make check" fails
34 5.6. liblzma.so (or similar) not found when running xz
37 0. Preface
38 ----------
40 If you aren't familiar with building packages that use GNU Autotools,
41 see the file INSTALL.generic for generic instructions before reading
42 further.
44 If you are going to build a package for distribution, see also the
45 file PACKAGERS. It contains information that should help making the
46 binary packages as good as possible, but the information isn't very
47 interesting to those making local builds for private use or for use
48 in special situations like embedded systems.
51 1. Supported platforms
52 ----------------------
54 XZ Utils are developed on GNU/Linux, but they should work on many
55 POSIX-like operating systems like *BSDs and Solaris, and even on
56 a few non-POSIX operating systems.
59 1.1. Compilers
61 A C99 compiler is required to compile XZ Utils. If you use GCC, you
62 need at least version 3.x.x. GCC version 2.xx.x doesn't support some
63 C99 features used in XZ Utils source code, thus GCC 2 won't compile
64 XZ Utils.
66 XZ Utils takes advantage of some GNU C extensions when building
67 with GCC. Because these extensions are used only when building
68 with GCC, it should be possible to use any C99 compiler.
71 1.2. Platform-specific notes
73 1.2.1. AIX
75 If you use IBM XL C compiler, pass CC=xlc_r to configure. If
76 you use CC=xlc instead, you must disable threading support
77 with --disable-threads (usually not recommended).
80 1.2.2. IRIX
82 MIPSpro 7.4.4m has been reported to produce broken code if using
83 the -O2 optimization flag ("make check" fails). Using -O1 should
84 work.
86 A problem has been reported when using shared liblzma. Passing
87 --disable-shared to configure works around this. Alternatively,
88 putting "-64" to CFLAGS to build a 64-bit version might help too.
91 1.2.3. MINIX 3
93 The default install of MINIX 3 includes Amsterdam Compiler Kit (ACK),
94 which doesn't support C99. Install GCC to compile XZ Utils.
96 MINIX 3.1.8 and older have bugs in /usr/include/stdint.h, which has
97 to be patched before XZ Utils can be compiled correctly. See
98 <http://gforge.cs.vu.nl/gf/project/minix/tracker/?action=TrackerItemEdit&tracker_item_id=537>.
100 MINIX 3.2.0 and later use a different libc and aren't affected by
101 the above bug.
103 XZ Utils doesn't have code to detect the amount of physical RAM and
104 number of CPU cores on MINIX 3.
106 See section 5.4 in this file about symbol visibility warnings (you
107 may want to pass gl_cv_cc_visibility=no to configure).
110 1.2.4. OpenVMS
112 XZ Utils can be built for OpenVMS, but the build system files
113 are not included in the XZ Utils source package. The required
114 OpenVMS-specific files are maintained by Jouk Jansen and can be
115 downloaded here:
117 http://nchrem.tnw.tudelft.nl/openvms/software2.html#xzutils
120 1.2.5. Solaris, OpenSolaris, and derivatives
122 The following linker error has been reported on some x86 systems:
124 ld: fatal: relocation error: R_386_GOTOFF: ...
126 This can be worked around by passing gl_cv_cc_visibility=no
127 as an argument to the configure script.
129 test_scripts.sh in "make check" may fail if good enough tools are
130 missing from PATH (/usr/xpg4/bin or /usr/xpg6/bin). Nowadays
131 /usr/xpg4/bin is added to the script PATH by default on Solaris
132 (see --enable-path-for-scripts=PREFIX in section 2), but old xz
133 releases needed extra steps. See sections 5.5 and 3.2 for more
134 information.
137 1.2.6. Tru64
139 If you try to use the native C compiler on Tru64 (passing CC=cc to
140 configure), you may need the workaround mention in section 5.1 in
141 this file (pass also ac_cv_prog_cc_c99= to configure).
144 1.2.7. Windows
146 The "windows" directory contains instructions for a few types
147 of builds:
149 - INSTALL-MinGW-w64_with_CMake.txt
150 Simple instructions how to build XZ Utils natively on
151 Windows using only CMake and a prebuilt toolchain
152 (GCC + MinGW-w64 or Clang/LLVM + MinGW-w64).
154 - INSTALL-MinGW-w64_with_Autotools.txt
155 Native build under MSYS2 or cross-compilation from
156 GNU/Linux using a bash script that creates a .zip
157 and .7z archives of the binaries and documentation.
158 The related file README-Windows.txt is for the
159 resulting binary package.
161 - INSTALL-MSVC.txt
162 Building with MSVC / Visual Studio and CMake.
164 - liblzma-crt-mixing.txt
165 Documentation what to take into account as a programmer
166 if liblzma.dll and the application don't use the same
167 CRT (MSVCRT or UCRT).
169 Other choices:
171 - Cygwin: https://cygwin.com/
172 Building on Cygwin can be done like on many POSIX operating
173 systems. XZ Utils >= 5.2.0 isn't compatible with Cygwin older
174 than 1.7.35 (data loss!). 1.7.35 was released on 2015-03-04.
176 - MSYS2: https://www.msys2.org/
179 1.2.8. DOS
181 There is a Makefile in the "dos" directory to build XZ Utils on
182 DOS using DJGPP. Support for long file names (LFN) is needed at
183 build time but the resulting xz.exe works without LFN support too.
184 See dos/INSTALL.txt and dos/README.txt for more information.
187 1.2.9. z/OS
189 To build XZ Utils on z/OS UNIX System Services using xlc, pass
190 these options to the configure script: CC='xlc -qhaltonmsg=CCN3296'
191 CPPFLAS='-D_UNIX03_THREADS -D_XOPEN_SOURCE=600'. The first makes
192 xlc throw an error if a header file is missing, which is required
193 to make the tests in configure work. The CPPFLAGS are needed to
194 get pthread support (some other CPPFLAGS may work too; if there
195 are problems, try -D_UNIX95_THREADS instead of -D_UNIX03_THREADS).
197 test_scripts.sh in "make check" will fail even if the scripts
198 actually work because the test data includes compressed files
199 with US-ASCII text.
201 No other tests should fail. If test_files.sh fails, check that
202 the included .xz test files weren't affected by EBCDIC conversion.
204 XZ Utils doesn't have code to detect the amount of physical RAM and
205 number of CPU cores on z/OS.
208 1.3. Adding support for new platforms
210 If you have written patches to make XZ Utils to work on previously
211 unsupported platform, please send the patches to me! I will consider
212 including them to the official version. It's nice to minimize the
213 need of third-party patching.
215 One exception: Don't request or send patches to change the whole
216 source package to C89. I find C99 substantially nicer to write and
217 maintain. However, the public library headers must be in C89 to
218 avoid frustrating those who maintain programs, which are strictly
219 in C89 or C++.
222 2. configure options
223 --------------------
225 In most cases, the defaults are what you want. Many of the options
226 below are useful only when building a size-optimized version of
227 liblzma or command line tools.
229 --enable-encoders=LIST
230 --disable-encoders
231 Specify a comma-separated LIST of filter encoders to
232 build. See "./configure --help" for exact list of
233 available filter encoders. The default is to build all
234 supported encoders.
236 If LIST is empty or --disable-encoders is used, no filter
237 encoders will be built and also the code shared between
238 encoders will be omitted.
240 Disabling encoders will remove some symbols from the
241 liblzma ABI, so this option should be used only when it
242 is known to not cause problems.
244 --enable-decoders=LIST
245 --disable-decoders
246 This is like --enable-encoders but for decoders. The
247 default is to build all supported decoders.
249 --enable-match-finders=LIST
250 liblzma includes two categories of match finders:
251 hash chains and binary trees. Hash chains (hc3 and hc4)
252 are quite fast but they don't provide the best compression
253 ratio. Binary trees (bt2, bt3 and bt4) give excellent
254 compression ratio, but they are slower and need more
255 memory than hash chains.
257 You need to enable at least one match finder to build the
258 LZMA1 or LZMA2 filter encoders. Usually hash chains are
259 used only in the fast mode, while binary trees are used to
260 when the best compression ratio is wanted.
262 The default is to build all the match finders if LZMA1
263 or LZMA2 filter encoders are being built.
265 --enable-checks=LIST
266 liblzma support multiple integrity checks. CRC32 is
267 mandatory, and cannot be omitted. See "./configure --help"
268 for exact list of available integrity check types.
270 liblzma and the command line tools can decompress files
271 which use unsupported integrity check type, but naturally
272 the file integrity cannot be verified in that case.
274 Disabling integrity checks may remove some symbols from
275 the liblzma ABI, so this option should be used only when
276 it is known to not cause problems.
278 --enable-external-sha256
279 Try to use SHA-256 code from the operating system libc
280 or similar base system libraries. This doesn't try to
281 use OpenSSL or libgcrypt or such libraries.
283 The reasons to use this option:
285 - It makes liblzma slightly smaller.
287 - It might improve SHA-256 speed if the implementation
288 in the operating is very good (but see below).
290 External SHA-256 is disabled by default for two reasons:
292 - On some operating systems the symbol names of the
293 SHA-256 functions conflict with OpenSSL's libcrypto.
294 This causes weird problems such as decompression
295 errors if an application is linked against both
296 liblzma and libcrypto. This problem affects at least
297 FreeBSD 10 and older and MINIX 3.3.0 and older, but
298 other OSes that provide a function "SHA256_Init" might
299 also be affected. FreeBSD 11 has the problem fixed.
300 NetBSD had the problem but it was fixed it in 2009
301 already. OpenBSD uses "SHA256Init" and thus never had
302 a conflict with libcrypto.
304 - The SHA-256 code in liblzma is faster than the SHA-256
305 code provided by some operating systems. If you are
306 curious, build two copies of xz (internal and external
307 SHA-256) and compare the decompression (xz --test)
308 times:
310 dd if=/dev/zero bs=1024k count=1024 \
311 | xz -v -0 -Csha256 > foo.xz
312 time xz --test foo.xz
314 --disable-microlzma
315 Don't build MicroLZMA encoder and decoder. This omits
316 lzma_microlzma_encoder() and lzma_microlzma_decoder()
317 API functions from liblzma. These functions are needed
318 by specific applications only. They were written for
319 erofs-utils but they may be used by others too.
321 --disable-lzip-decoder
322 Disable decompression support for .lz (lzip) files.
323 This omits the API function lzma_lzip_decoder() from
324 liblzma and .lz support from the xz tool.
326 --disable-xz
327 --disable-xzdec
328 --disable-lzmadec
329 --disable-lzmainfo
330 Don't build and install the command line tool mentioned
331 in the option name.
333 NOTE: Disabling xz will skip some tests in "make check".
335 NOTE: If xzdec is disabled and lzmadec is left enabled,
336 a dangling man page symlink lzmadec.1 -> xzdec.1 is
337 created.
339 --disable-lzma-links
340 Don't create symlinks for LZMA Utils compatibility.
341 This includes lzma, unlzma, and lzcat. If scripts are
342 installed, also lzdiff, lzcmp, lzgrep, lzegrep, lzfgrep,
343 lzmore, and lzless will be omitted if this option is used.
345 --disable-scripts
346 Don't install the scripts xzdiff, xzgrep, xzmore, xzless,
347 and their symlinks.
349 --disable-doc
350 Don't install the documentation files to $docdir
351 (often /usr/doc/xz or /usr/local/doc/xz). Man pages
352 will still be installed. The $docdir can be changed
353 with --docdir=DIR.
355 --disable-assembler
356 This disables CRC32 and CRC64 assembly code on
357 32-bit x86. This option currently does nothing
358 on other architectures (not even on x86-64).
360 The 32-bit x86 assembly is position-independent code
361 which is suitable for use in shared libraries and
362 position-independent executables. It uses only i386
363 instructions but the code is optimized for i686 class
364 CPUs. If you are compiling liblzma exclusively for
365 pre-i686 systems, you may want to disable the assembler
366 code.
368 --disable-clmul-crc
369 Disable the use of carryless multiplication for CRC
370 calculation even if compiler support for it is detected.
371 The code uses runtime detection of SSSE3, SSE4.1, and
372 CLMUL instructions on x86. On 32-bit x86 this currently
373 is used only if --disable-assembler is used (this might
374 be fixed in the future). The code works on E2K too.
376 If using compiler options that unconditionally allow the
377 required extensions (-msse4.1 -mpclmul) then runtime
378 detection isn't used and the generic code is omitted.
380 --disable-arm64-crc32
381 Disable the use of the ARM64 CRC32 instruction extension
382 even if compiler support for it is detected. The code will
383 detect support for the instruction at runtime.
385 If using compiler options that unconditionally allow the
386 required extensions (-march=armv8-a+crc or -march=armv8.1-a
387 and later) then runtime detection isn't used and the
388 generic code is omitted.
390 --enable-unaligned-access
391 Allow liblzma to use unaligned memory access for 16-bit,
392 32-bit, and 64-bit loads and stores. This should be
393 enabled only when the hardware supports this, that is,
394 when unaligned access is fast. Some operating system
395 kernels emulate unaligned access, which is extremely
396 slow. This option shouldn't be used on systems that
397 rely on such emulation.
399 Unaligned access is enabled by default on these:
400 - 32-bit x86
401 - 64-bit x86-64
402 - 32-bit big endian PowerPC
403 - 64-bit big endian PowerPC
404 - 64-bit little endian PowerPC
405 - some RISC-V [1]
406 - some 32-bit ARM [2]
407 - some 64-bit ARM64 [2] (NOTE: Autodetection bug
408 if using GCC -mstrict-align, see below.)
410 [1] Unaligned access is enabled by default if
411 configure sees that the C compiler
412 #defines __riscv_misaligned_fast.
414 [2] Unaligned access is enabled by default if
415 configure sees that the C compiler
416 #defines __ARM_FEATURE_UNALIGNED:
418 - ARMv7 + GCC or Clang: It works. The options
419 -munaligned-access and -mno-unaligned-access
420 affect this macro correctly.
422 - ARM64 + Clang: It works. The options
423 -munaligned-access, -mno-unaligned-access,
424 and -mstrict-align affect this macro correctly.
425 Clang >= 17 supports -mno-strict-align too.
427 - ARM64 + GCC: It partially works. The macro
428 is always #defined by GCC versions at least
429 up to 13.2, even when using -mstrict-align.
430 If building for strict-align ARM64, the
431 configure option --disable-unaligned-access
432 should be used if using a GCC version that has
433 this issue because otherwise the performance
434 may be degraded. It likely won't crash due to
435 how unaligned access is done in the C code.
437 --enable-unsafe-type-punning
438 This enables use of code like
440 uint8_t *buf8 = ...;
441 *(uint32_t *)buf8 = ...;
443 which violates strict aliasing rules and may result
444 in broken code. There should be no need to use this
445 option with recent GCC or Clang versions on any
446 arch as just as fast code can be generated in a safe
447 way too (using __builtin_assume_aligned + memcpy).
449 However, this option might improve performance in some
450 other cases, especially with old compilers (for example,
451 GCC 3 and early 4.x on x86, GCC < 6 on ARMv6 and ARMv7).
453 --enable-small
454 Reduce the size of liblzma by selecting smaller but
455 semantically equivalent version of some functions, and
456 omit precomputed lookup tables. This option tends to
457 make liblzma slightly slower.
459 Note that while omitting the precomputed tables makes
460 liblzma smaller on disk, the tables are still needed at
461 run time, and need to be computed at startup. This also
462 means that the RAM holding the tables won't be shared
463 between applications linked against shared liblzma.
465 This option doesn't modify CFLAGS to tell the compiler
466 to optimize for size. You need to add -Os or equivalent
467 flag(s) to CFLAGS manually.
469 --enable-assume-ram=SIZE
470 On the most common operating systems, XZ Utils is able to
471 detect the amount of physical memory on the system. This
472 information is used by the options --memlimit-compress,
473 --memlimit-decompress, and --memlimit when setting the
474 limit to a percentage of total RAM.
476 On some systems, there is no code to detect the amount of
477 RAM though. Using --enable-assume-ram one can set how much
478 memory to assume on these systems. SIZE is given as MiB.
479 The default is 128 MiB.
481 Feel free to send patches to add support for detecting
482 the amount of RAM on the operating system you use. See
483 src/common/tuklib_physmem.c for details.
485 --enable-threads=METHOD
486 Threading support is enabled by default so normally there
487 is no need to specify this option.
489 Supported values for METHOD:
491 yes Autodetect the threading method. If none
492 is found, configure will give an error.
494 posix Use POSIX pthreads. This is the default
495 except on Windows outside Cygwin.
497 win95 Use Windows 95 compatible threads. This
498 is compatible with Windows XP and later
499 too. This is the default for 32-bit x86
500 Windows builds. Unless the compiler
501 supports __attribute__((__constructor__)),
502 the 'win95' threading is incompatible with
503 --enable-small.
505 vista Use Windows Vista compatible threads. The
506 resulting binaries won't run on Windows XP
507 or older. This is the default for Windows
508 excluding 32-bit x86 builds (that is, on
509 x86-64 the default is 'vista').
511 no Disable threading support. This is the
512 same as using --disable-threads.
513 NOTE: If combined with --enable-small
514 and the compiler doesn't support
515 __attribute__((__constructor__)), the
516 resulting liblzma won't be thread safe,
517 that is, if a multi-threaded application
518 calls any liblzma functions from more than
519 one thread, something bad may happen.
521 --enable-ifunc
522 Use __attribute__((__ifunc__())) in liblzma. This is
523 enabled by default on GNU/Linux and FreeBSD.
525 The ifunc attribute is incompatible with
526 -fsanitize=address. --disable-ifunc must be used
527 if any -fsanitize= option is specified in CFLAGS.
529 --enable-sandbox=METHOD
530 There is limited sandboxing support in the xz and xzdec
531 tools. If built with sandbox support, xz uses it
532 automatically when (de)compressing exactly one file to
533 standard output when the options --files or --files0 aren't
534 used. This is a common use case, for example,
535 (de)compressing .tar.xz files via GNU tar. The sandbox is
536 also used for single-file 'xz --test' or 'xz --list'.
537 xzdec always uses the sandbox, except when more than one
538 file are decompressed. In this case it will enable the
539 sandbox for the last file that is decompressed.
541 Supported METHODs:
543 auto Look for a supported sandboxing method
544 and use it if found. If no method is
545 found, then sandboxing isn't used.
546 This is the default.
548 no Disable sandboxing support.
550 capsicum
551 Use Capsicum (FreeBSD >= 10.2) for
552 sandboxing. If no Capsicum support
553 is found, configure will give an error.
555 pledge Use pledge(2) (OpenBSD >= 5.9) for
556 sandboxing. If pledge(2) isn't found,
557 configure will give an error.
559 landlock
560 Use Landlock (Linux >= 5.13) for
561 sandboxing. If no Landlock support
562 is found, configure will give an error.
564 --enable-symbol-versions
565 Use symbol versioning for liblzma. This is enabled by
566 default on GNU/Linux, other GNU-based systems, and
567 FreeBSD.
569 --enable-debug
570 This enables the assert() macro and possibly some other
571 run-time consistency checks. It makes the code slower, so
572 you normally don't want to have this enabled.
574 --enable-werror
575 If building with GCC, make all compiler warnings an error,
576 that abort the compilation. This may help catching bugs,
577 and should work on most systems. This has no effect on the
578 resulting binaries.
580 --enable-path-for-scripts=PREFIX
581 If PREFIX isn't empty, PATH=PREFIX:$PATH will be set in
582 the beginning of the scripts (xzgrep and others).
583 The default is empty except on Solaris the default is
584 /usr/xpg4/bin.
586 This can be useful if the default PATH doesn't contain
587 modern POSIX tools (as can be the case on Solaris) or if
588 one wants to ensure that the correct xz binary is in the
589 PATH for the scripts. Note that the latter use can break
590 "make check" if the prefixed PATH causes a wrong xz binary
591 (other than the one that was just built) to be used.
593 Older xz releases support a different method for setting
594 the PATH for the scripts. It is described in section 3.2
595 and is supported in this xz version too.
598 2.1. Static vs. dynamic linking of liblzma
600 On 32-bit x86, linking against static liblzma can give a minor
601 speed improvement. Static libraries on x86 are usually compiled as
602 position-dependent code (non-PIC) and shared libraries are built as
603 position-independent code (PIC). PIC wastes one register, which can
604 make the code slightly slower compared to a non-PIC version. (Note
605 that this doesn't apply to x86-64.)
607 If you want to link xz against static liblzma, the simplest way
608 is to pass --disable-shared to configure. If you want also shared
609 liblzma, run configure again and run "make install" only for
610 src/liblzma.
613 2.2. Optimizing xzdec and lzmadec
615 xzdec and lzmadec are intended to be relatively small instead of
616 optimizing for the best speed. Thus, it is a good idea to build
617 xzdec and lzmadec separately:
619 - To link the tools against static liblzma, pass --disable-shared
620 to configure.
622 - To select somewhat size-optimized variant of some things in
623 liblzma, pass --enable-small to configure.
625 - Tell the compiler to optimize for size instead of speed.
626 For example, with GCC, put -Os into CFLAGS.
628 - xzdec and lzmadec will never use multithreading capabilities of
629 liblzma. You can avoid dependency on libpthread by passing
630 --disable-threads to configure.
632 - There are and will be no translated messages for xzdec and
633 lzmadec, so it is fine to pass also --disable-nls to configure.
635 - Only decoder code is needed, so you can speed up the build
636 slightly by passing --disable-encoders to configure. This
637 shouldn't affect the final size of the executables though,
638 because the linker is able to omit the encoder code anyway.
640 If you have no use for xzdec or lzmadec, you can disable them with
641 --disable-xzdec and --disable-lzmadec.
644 3. xzgrep and other scripts
645 ---------------------------
647 3.1. Dependencies
649 POSIX shell (sh) and bunch of other standard POSIX tools are required
650 to run the scripts. The configure script tries to find a POSIX
651 compliant sh, but if it fails, you can force the shell by passing
652 gl_cv_posix_shell=/path/to/posix-sh as an argument to the configure
653 script.
655 xzdiff (xzcmp/lzdiff/lzcmp) may use mktemp if it is available. As
656 a fallback xzdiff will use mkdir to securely create a temporary
657 directory. Having mktemp available is still recommended since the
658 mkdir fallback method isn't as robust as mktemp is. The original
659 mktemp can be found from <https://www.mktemp.org/>. On GNU, most will
660 use the mktemp program from GNU coreutils instead of the original
661 implementation. Both mktemp versions are fine.
663 In addition to using xz to decompress .xz files, xzgrep and xzdiff
664 use gzip, bzip2, and lzop to support .gz, bz2, and .lzo files.
667 3.2. PATH
669 The method described below is supported by older xz releases.
670 It is supported by the current version too, but the newer
671 --enable-path-for-scripts=PREFIX described in section 2 may be
672 more convenient.
674 The scripts assume that the required tools (standard POSIX utilities,
675 mktemp, and xz) are in PATH; the scripts don't set the PATH themselves
676 (except as described for --enable-path-for-scripts=PREFIX). Some
677 people like this while some think this is a bug. Those in the latter
678 group can easily patch the scripts before running the configure script
679 by taking advantage of a placeholder line in the scripts.
681 For example, to make the scripts prefix /usr/bin:/bin to PATH:
683 perl -pi -e 's|^#SET_PATH.*$|PATH=/usr/bin:/bin:\$PATH|' \
684 src/scripts/xz*.in
687 4. Tests
688 --------
690 The test framework can be built and run by executing "make check" in
691 the build directory. The tests are a mix of executables and POSIX
692 shell scripts (sh). All tests should pass if the default configuration
693 is used. Disabling features through the configure options may cause
694 some tests to be skipped. If any tests do not pass, see section 5.5.
697 4.1. Testing in parallel
699 The tests can be run in parallel using the "-j" make option on systems
700 that support it. For instance, "make -j4 check" will run up to four
701 tests simultaneously.
704 4.2. Cross compiling
706 The tests can be built without running them:
708 make check TESTS=
710 The TESTS variable is the list of tests you wish to run. Leaving it
711 empty will compile the tests without running any.
713 If the tests are copied to a target machine to execute, the test data
714 files in the directory tests/files must also be copied. The tests
715 search for the data files using the environment variable $srcdir,
716 expecting to find the data files under $srcdir/files/. If $srcdir
717 isn't set then it defaults to the current directory.
719 The shell script tests can be copied from the source directory to the
720 target machine to execute. In addition to the test files, these tests
721 will expect the following relative file paths to execute properly:
723 ./create_compress_files
724 ../config.h
725 ../src/xz/xz
726 ../src/xzdec/xzdec
727 ../src/scripts/xzdiff
728 ../src/scripts/xzgrep
731 5. Troubleshooting
732 ------------------
734 5.1. "No C99 compiler was found."
736 You need a C99 compiler to build XZ Utils. If the configure script
737 cannot find a C99 compiler and you think you have such a compiler
738 installed, set the compiler command by passing CC=/path/to/c99 as
739 an argument to the configure script.
741 If you get this error even when you think your compiler supports C99,
742 you can override the test by passing ac_cv_prog_cc_c99= as an argument
743 to the configure script. The test for C99 compiler is not perfect (and
744 it is not as easy to make it perfect as it sounds), so sometimes this
745 may be needed. You will get a compile error if your compiler doesn't
746 support enough C99.
749 5.2. "No POSIX conforming shell (sh) was found."
751 xzgrep and other scripts need a shell that (roughly) conforms
752 to POSIX. The configure script tries to find such a shell. If
753 it fails, you can force the shell to be used by passing
754 gl_cv_posix_shell=/path/to/posix-sh as an argument to the configure
755 script. Alternatively you can omit the installation of scripts and
756 this error by passing --disable-scripts to configure.
759 5.3. configure works but build fails at crc32_x86.S
761 The easy fix is to pass --disable-assembler to the configure script.
763 The configure script determines if assembler code can be used by
764 looking at the configure triplet; there is currently no check if
765 the assembler code can actually actually be built. The x86 assembler
766 code should work on x86 GNU/Linux, *BSDs, Solaris, Darwin, MinGW,
767 Cygwin, and DJGPP. On other x86 systems, there may be problems and
768 the assembler code may need to be disabled with the configure option.
770 If you get this error when building for x86-64, you have specified or
771 the configure script has misguessed your architecture. Pass the
772 correct configure triplet using the --build=CPU-COMPANY-SYSTEM option
773 (see INSTALL.generic).
776 5.4. Lots of warnings about symbol visibility
778 On some systems where symbol visibility isn't supported, GCC may
779 still accept the visibility options and attributes, which will make
780 configure think that visibility is supported. This will result in
781 many compiler warnings. You can avoid the warnings by forcing the
782 visibility support off by passing gl_cv_cc_visibility=no as an
783 argument to the configure script. This has no effect on the
784 resulting binaries, but fewer warnings looks nicer and may allow
785 using --enable-werror.
788 5.5. "make check" fails
790 If the other tests pass but test_scripts.sh fails, then the problem
791 is in the scripts in src/scripts. Comparing the contents of
792 tests/xzgrep_test_output to tests/xzgrep_expected_output might
793 give a good idea about problems in xzgrep. One possibility is that
794 some tools are missing from the current PATH or the tools lack
795 support for some POSIX features. This can happen at least on
796 Solaris where the tools in /bin may be ancient but good enough
797 tools are available in /usr/xpg4/bin or /usr/xpg6/bin. For possible
798 fixes, see --enable-path-for-scripts=PREFIX in section 2 and the
799 older alternative method described in section 3.2 of this file.
801 If tests other than test_scripts.sh fail, a likely reason is that
802 libtool links the test programs against an installed version of
803 liblzma instead of the version that was just built. This is
804 obviously a bug which seems to happen on some platforms.
805 A workaround is to uninstall the old liblzma versions first.
807 If the problem isn't any of those described above, then it's likely
808 a bug in XZ Utils or in the compiler. See the platform-specific
809 notes in this file for possible known problems. Please report
810 a bug if you cannot solve the problem. See README for contact
811 information.
814 5.6. liblzma.so (or similar) not found when running xz
816 If you installed the package with "make install" and get an error
817 about liblzma.so (or a similarly named file) being missing, try
818 running "ldconfig" to update the run-time linker cache (if your
819 operating system has such a command).