Changeset c91dd5b for chapter05/coreutils.xml
- Timestamp:
- 02/11/2004 10:02:10 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, v5_1, v5_1_1, 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:
- a0b689e
- Parents:
- 5cd6caa
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/coreutils.xml
r5cd6caa rc91dd5b 19 19 20 20 <para>Coreutils has an issue when compiled against Glibc-&glibc-version;. 21 Without the patch below, some of the Coreutils utilities (head, tail, sort etc) 22 will reject their traditional syntax which has been in use for approximately 30 23 years. The old syntax is so pervasive that compatibility must be preserved until 24 the many places where it is used can be updated. More details are provided in 25 the comments inside the patch itself. Use of this patch is by no means 26 compulsory but opting not to use it means you'll have deal with the consequences 27 yourself, i.e. patch the many software packages that use the old syntax. Apply 28 the patch:</para> 21 Without the patch below, some of the Coreutils utilities 22 (<command>head</command>, <command>tail</command>, <command>sort</command>, 23 and others) will reject their traditional syntax which has been in use for 24 approximately 30 years. This old syntax is so pervasive that compatibility 25 should be preserved until the many places where it is used can be updated. 26 More details on this are provided in the comments inside the patch itself. Use 27 of this patch is by no means compulsory, but not using it means you'll have to 28 deal with the consequences yourself: patch the many packages that use the old 29 syntax. Therefore, better apply the patch:</para> 29 30 30 31 <screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen> … … 38 39 <screen><userinput>make</userinput></screen> 39 40 40 <para>As discussed earlier, we don't recommend running the test suites for the 41 temporary tools here in this chapter. If you still want to run the Coreutils 42 test suite anyway, the following command will do so:</para> 43 44 <screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen> 45 46 <para>The meaning of the make parameter:</para> 47 48 <itemizedlist> 49 <listitem><para><userinput>RUN_EXPENSIVE_TESTS=yes</userinput>: This tells the 50 test suite to run several additional tests that are considered relatively 51 expensive on some platforms. However, they are generally not a problem on 52 Linux.</para></listitem> 53 </itemizedlist> 41 <para>(If you insist on testing the results, then issue: 42 <userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput>. The 43 <emphasis>RUN_EXPENSIVE_TESTS=yes</emphasis> parameter tells the test suite to 44 run several additional tests that are considered relatively expensive on some 45 platforms but generally are not a problem on Linux.)</para> 54 46 55 47 <para>And install the package:</para>
Note:
See TracChangeset
for help on using the changeset viewer.