Changeset 5864a166 for general/prog
- Timestamp:
- 07/30/2023 09:15:35 PM (14 months ago)
- Branches:
- 12.0, 12.1, 12.2, gimp3, ken/TL2024, ken/tuningfonts, lazarus, plabs/newcss, python3.11, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/for-12.3, xry111/llvm18, xry111/spidermonkey128
- Children:
- 3cf0475
- Parents:
- dfb8390
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/gcc.xml
rdfb8390 r5864a166 8 8 <!ENTITY gcc-download-ftp "&gnu-ftp;/gcc/gcc-&gcc-version;/gcc-&gcc-version;.tar.xz"> 9 9 <!-- Update this also on the grub-uefi page --> 10 <!ENTITY gcc-md5sum " 43e4de77f2218c83ca675257ea1af9ef">11 <!ENTITY gcc-size "8 3MB">12 <!ENTITY gcc-buildsize " 9.6 GB (2.4 GB installed with all listed languages; add 1.4GB for tests)">13 <!ENTITY gcc-time " 32 SBU (add 55 SBU for tests; both with parallelism=4)">10 <!ENTITY gcc-md5sum "e0e48554cc6e4f261d55ddee9ab69075"> 11 <!ENTITY gcc-size "84 MB"> 12 <!ENTITY gcc-buildsize "13 GB (2.9 GB installed with all listed languages; add 1.5 GB for tests)"> 13 <!ENTITY gcc-time "13 SBU (add 29 SBU for tests; both with parallelism=8)"> 14 14 ]> 15 15 … … 64 64 compiled during LFS. 65 65 </para> 66 <!--67 <para>68 Some system headers need to be fixed to be used with GCC. This is done69 during the installation of GCC, and the <quote>fixed</quote> headers70 are installed in <filename class="directory">71 /usr/lib/gcc/<machine triplet>/<GCC version>/include-fixed72 </filename>. This is harmless if GCC is built during the LFS stage. But73 if you reinstall GCC in BLFS, some of the BLFS packages may be74 <quote>fixed</quote>. If one of those packages is reinstalled75 afterwards, the <quote>fixed</quote> headers are not updated, which may76 lead to version mismatches. In case that happens, the77 <quote>fixed</quote> headers must be updated by running (as78 <systemitem class="username">root</systemitem>):79 <command>80 /usr/libexec/gcc/x86_64-pc-linux-gnu/&gcc-version;/install-tools/mkheaders81 </command>. The machine triplet may be different on a 32-bit system.82 </para>83 -->84 66 </caution> 85 67 … … 173 155 <command>./configure</command> options below. 174 156 </para> 175 <!-- 176 <para> 177 Some packages checks on the phrase <literal>gccgo</literal> in the output 178 of <command>go version</command> to see which kind of Go compiler is 179 installed (gcc-go or golang). The absence of <literal>gccgo</literal> in 180 that string makes them to assume the compiler is the golang which is wrong. 181 If Go isn't in the list of desired languages, this patch can be skipped 182 while it does not harm if applied anyway. Fix the Go part of gcc to show 183 a valid version string when calling <command>go version</command> by 184 applying a patch: 185 </para> 186 187 <screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-fix_go_version-1.patch</userinput></screen> 188 --> 157 189 158 <para> 190 159 Install <application>GCC</application> by running the following commands: … … 215 184 the <application>gcc</application> part of the test suite will run more 216 185 tests than in LFS. Some of those will report FAIL and others XPASS 217 (pass when expected to FAIL). As of gcc-13. 1.0, about 60FAIL occur186 (pass when expected to FAIL). As of gcc-13.2.0, about 65 FAIL occur 218 187 in the <quote>guality</quote> suite, as well as miscellaneous failures 219 188 throughout the rest of the test suite. 220 189 If all the compilers above are built, there will be a little over 80 221 unexpected failures out of over 478,000 tests. To run the tests, issue:190 unexpected failures out of over 546,000 tests. To run the tests, issue: 222 191 </para> 223 192 … … 246 215 chown -v -R root:root \ 247 216 /usr/lib/gcc/*linux-gnu/&gcc-version;/include{,-fixed}</userinput></screen> 248 249 <para>250 Some packages expect to find the C preprocessor in251 <filename class="directory">/lib</filename> or may refer to the C compiler252 under the name <command>cc</command>. The following symbolic links are not253 needed if you have followed the LFS instructions, since they254 have been already created. If you do not have them on your system, issue255 as the <systemitem class="username">root</systemitem> user:256 </para>257 258 <screen role="root"><userinput>ln -v -sf ../usr/bin/cpp /lib &&259 ln -v -sf gcc /usr/bin/cc &&260 install -v -dm755 /usr/lib/bfd-plugins &&261 ln -sfv ../../libexec/gcc/$(gcc -dumpmachine)/&gcc-version;/liblto_plugin.so /usr/lib/bfd-plugins/</userinput></screen>262 217 263 218 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.