Changeset e4b4c5a0 for chapter08/gcc.xml
- Timestamp:
- 07/01/2024 06:59:19 AM (3 months ago)
- Branches:
- xry111/clfs-ng
- Children:
- 2b63974
- Parents:
- fe48a03 (diff), 201aa93 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/gcc.xml
rfe48a03 re4b4c5a0 41 41 <sect2 role="installation"> 42 42 <title>Installation of GCC</title> 43 <!--44 <para>At first, fix an issue breaking45 <filename class="libraryfile">libasan.a</filename> building this package46 with Glibc-2.34 or later:</para>47 48 <screen><userinput remap="pre">sed -e '/static.*SIGSTKSZ/d' \49 -e 's/return kAltStackSize/return SIGSTKSZ * 4/' \50 -i libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp</userinput></screen>51 -->52 <!--53 <para>First fix a problem with the latest version of glibc:</para>54 55 <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen>56 -->57 43 58 44 <para>For x86_64 target, set the default directory name for … … 76 62 --enable-default-pie \ 77 63 --enable-default-ssp \ 64 --enable-host-pie \ 78 65 --disable-multilib \ 79 66 --disable-bootstrap \ … … 147 134 important, but it takes a long time. First-time builders are 148 135 encouraged to run the test suite. The time to run the tests can be 149 reduced significantly by adding -jx to the <command>make -k check</command> command below,150 where x is the number of CPU cores on your system.</para>136 reduced significantly by adding -jx to the <command>make -k check</command> 137 command below, where x is the number of CPU cores on your system.</para> 151 138 </important> 152 139 … … 155 142 156 143 <screen><userinput remap="test">ulimit -s 32768</userinput></screen> 144 145 <para>Now remove/fix several known test failures:</para> 146 147 <screen><userinput remap="test">sed -e '/cpython/d' -i ../gcc/testsuite/gcc.dg/plugin/plugin.exp 148 sed -e 's/no-pic /&-no-pie /' -i ../gcc/testsuite/gcc.target/i386/pr113689-1.c 149 sed -e 's/300000/(1|300000)/' -i ../libgomp/testsuite/libgomp.c-c++-common/pr109062.c 150 sed -e 's/{ target nonpic } //' \ 151 -e '/GOTPCREL/d' -i ../gcc/testsuite/gcc.target/i386/fentryname3.c</userinput></screen> 157 152 158 153 <para>Test the results as a non-privileged user, but do not stop at errors:</para> … … 171 166 url="&test-results;"/> and 172 167 <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> 173 168 <!-- 174 169 <para> 175 170 Eight gcc tests (out of over 185,000): 176 <!- - https://gcc.gnu.org/PR106375 --><filename>pr56837.c</filename>171 <!- - https://gcc.gnu.org/PR106375 - -><filename>pr56837.c</filename> 177 172 and seven tests in the <filename class='directory'>analyzer</filename> 178 173 directory are known to fail. 179 174 180 <!- - https://gcc.gnu.org/PR109353 -->175 <!- - https://gcc.gnu.org/PR109353 - -> 181 176 One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is 182 177 known to fail. … … 190 185 <filename class='directory'>vect</filename> directory are known to fail 191 186 if the hardware does not support AVX.</para> 192 193 <para>A few unexpected failures cannot always be avoided. The GCC developers 194 are usually aware of these issues, but have not resolved them yet. 187 --> 188 <para>A few unexpected failures cannot always be avoided. In some cases 189 test failures depend on the specific hardware of the system.<!--The GCC developers 190 are usually aware of these issues, but have not resolved them yet.--> 195 191 Unless the test results are vastly different from those at the above URL, 196 192 it is safe to continue.</para>
Note:
See TracChangeset
for help on using the changeset viewer.