Changeset fa2e693 for chapter05/lockingglibc.xml
- Timestamp:
- 09/14/2003 09:16:58 AM (21 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_0, 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:
- 980599d
- Parents:
- 0bf1ea9
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/lockingglibc.xml
r0bf1ea9 rfa2e693 40 40 <para>Lastly, there is a possibility that some include files from the host 41 41 system have found their way into gcc's private include dir. This can happen 42 because of GCC's "fixincludes" process which part of the GCC build. We'll43 explain more about this further on in this chapter. For now, run the42 because of GCC's "fixincludes" process which runs as part of the GCC build. 43 We'll explain more about this further on in this chapter. For now, run the 44 44 following commands to eliminate this possibility.</para> 45 45
Note:
See TracChangeset
for help on using the changeset viewer.