Changeset ede9b9b for chapter05/coreutils.xml
- Timestamp:
- 02/25/2004 10:04:14 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:
- dd3e8c6
- Parents:
- e421d2e
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/coreutils.xml
re421d2e rede9b9b 18 18 <title>Installation of Coreutils</title> 19 19 20 <para> Coreutilshas an issue when compiled against Glibc-&glibc-version;.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 whichhas been in use for20 <para>This package has an issue when compiled against Glibc-&glibc-version;. 21 Without the patch below, some of the Coreutils utilities (such as 22 (<command>head</command>, <command>tail</command> and <command>sort</command>) 23 will reject their traditional syntax, a syntax that has been in use for 24 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 ofthis patch is by no means compulsory, but not using it means you'll have to28 deal with the consequences yourself: patch the many packages that use the old29 syntax. Therefore, better apply the patch:</para>25 should be preserved until the many places where it is used can be updated. More 26 details on this are provided in the comments inside the patch itself. Use of 27 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 still use the 29 old syntax. Therefore, better apply the patch:</para> 30 30 31 31 <screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen>
Note:
See TracChangeset
for help on using the changeset viewer.