Changeset 574b0ea for chapter05/coreutils.xml
- Timestamp:
- 05/30/2004 01:41:04 PM (20 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 07f719a
- Parents:
- b711e1d
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/coreutils.xml
rb711e1d r574b0ea 32 32 <screen><userinput>DEFAULT_POSIX2_VERSION=199209 ./configure --prefix=/tools</userinput></screen> 33 33 34 <para>This package has an issue when compiled against versions of glibc34 <para>This package has an issue when compiled against versions of Glibc 35 35 later than 2.3.2. Some of the Coreutils utilities (such as 36 36 (<command>head</command>, <command>tail</command> and <command>sort</command>) … … 39 39 should be preserved until the many places where it is used can be 40 40 updated. Backwards compatibility is achieved by setting the 41 DEFAULT_POSIX2_VERSION environment variable to "199209"in the above42 command. If you don 't want coreutils to be backwards compatible41 DEFAULT_POSIX2_VERSION environment variable to <quote>199209</quote> in the above 42 command. If you don't want coreutils to be backwards compatible 43 43 with the traditional syntax, then simply omit setting the DEFAULT_POSIX2_VERSION 44 environment variable. Realise though, that doing so will mean you 'll have44 environment variable. Realise though, that doing so will mean you'll have 45 45 to deal with the consequences yourself: patch the many packages that still use 46 46 the old syntax. We therefore recommend using the instructions exactly as given … … 53 53 <para>(If you insist on testing the results, then issue: 54 54 <userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput>. The 55 < emphasis>RUN_EXPENSIVE_TESTS=yes</emphasis> parameter tells the test suite to55 <parameter>RUN_EXPENSIVE_TESTS=yes</parameter> parameter tells the test suite to 56 56 run several additional tests that are considered relatively expensive on some 57 57 platforms but generally are not a problem on Linux.)</para>
Note:
See TracChangeset
for help on using the changeset viewer.