Changeset bc33d9d for chapter08/gcc.xml
- Timestamp:
- 05/12/2024 07:26:02 AM (6 weeks ago)
- Branches:
- multilib
- Children:
- 2f3fd748
- Parents:
- 94f7cd9 (diff), 340e17a (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
r94f7cd9 rbc33d9d 41 41 <sect2 role="installation"> 42 42 <title>Installation of GCC</title> 43 <!-- 44 <para>At first, fix an issue breaking 45 <filename class="libraryfile">libasan.a</filename> building this package 46 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 --> 43 57 44 <para>If building on x86_64, change the default directory name for 64-bit 58 45 libraries to <quote>lib</quote>:</para> … … 84 71 --enable-default-pie \ 85 72 --enable-default-ssp \ 73 --enable-host-pie \ 86 74 --disable-multilib \ 87 75 --disable-bootstrap \ … … 169 157 important, but it takes a long time. First-time builders are 170 158 encouraged to run the test suite. The time to run the tests can be 171 reduced significantly by adding -jx to the <command>make -k check</command> command below,172 where x is the number of CPU cores on your system.</para>159 reduced significantly by adding -jx to the <command>make -k check</command> 160 command below, where x is the number of CPU cores on your system.</para> 173 161 </important> 174 162 … … 177 165 178 166 <screen><userinput remap="test">ulimit -s 32768</userinput></screen> 167 168 <para>Now remove/fix several known test failures:</para> 169 170 <screen><userinput remap="test">sed -e '/cpython/d' -i ../gcc/testsuite/gcc.dg/plugin/plugin.exp 171 sed -e 's/no-pic /&-no-pie /' -i ../gcc/testsuite/gcc.target/i386/pr113689-1.c 172 sed -e 's/300000/(1|300000)/' -i ../libgomp/testsuite/libgomp.c-c++-common/pr109062.c 173 sed -e 's/{ target nonpic } //' \ 174 -e '/GOTPCREL/d' -i ../gcc/testsuite/gcc.target/i386/fentryname3.c</userinput></screen> 179 175 180 176 <para>Test the results as a non-privileged user, but do not stop at errors:</para> … … 193 189 url="&test-results;"/> and 194 190 <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> 195 191 <!-- 196 192 <para> 197 193 Eight gcc tests (out of over 185,000): 198 <!- - https://gcc.gnu.org/PR106375 --><filename>pr56837.c</filename>194 <!- - https://gcc.gnu.org/PR106375 - -><filename>pr56837.c</filename> 199 195 and seven tests in the <filename class='directory'>analyzer</filename> 200 196 directory are known to fail. 201 197 202 <!- - https://gcc.gnu.org/PR109353 -->198 <!- - https://gcc.gnu.org/PR109353 - -> 203 199 One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is 204 200 known to fail. … … 212 208 <filename class='directory'>vect</filename> directory are known to fail 213 209 if the hardware does not support AVX.</para> 214 215 <para>A few unexpected failures cannot always be avoided. The GCC developers 216 are usually aware of these issues, but have not resolved them yet. 210 --> 211 <para>A few unexpected failures cannot always be avoided. In some cases 212 test failures depend on the specific hardware of the system.<!--The GCC developers 213 are usually aware of these issues, but have not resolved them yet.--> 217 214 Unless the test results are vastly different from those at the above URL, 218 215 it is safe to continue.</para>
Note:
See TracChangeset
for help on using the changeset viewer.