Changes in chapter08/gcc.xml [cfcc2fe:b6ff6a8]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/gcc.xml
rcfcc2fe rb6ff6a8 55 55 <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen> 56 56 --> 57 <para>If building on x86_64, change the default directory name for 64-bit 58 libraries to <quote>lib</quote>:</para> 59 60 <screen><userinput remap="pre">case $(uname -m) in 61 x86_64) 62 sed -e '/m64=/s/lib64/lib/' \ 63 -i.orig gcc/config/i386/t-linux64 64 ;; 65 esac</userinput></screen> 57 <para>On ARM64 hosts, set the default directory name for 58 64-bit libraries to <quote>lib</quote>:</para> 59 60 <screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \ 61 -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen> 66 62 67 63 <para>The GCC documentation recommends building GCC in a dedicated build directory:</para> … … 173 169 <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> 174 170 175 <para><!--Two tests named <filename>pr104610.c</filename> and 176 <filename>pr69482-1.c</filename> are known to fail because the test 177 files does not account for the 178 <parameter>- -enable-default-ssp</parameter> option.--> 179 <!-- https://gcc.gnu.org/PR106375 and https://gcc.gnu.org/PR109353 --> 171 <para> 172 <!-- https://gcc.gnu.org/PR107915 and https://gcc.gnu.org/PR109353 --> 180 173 Two tests named <filename>copy.cc</filename> and 181 <filename>pr56837.c</filename> are known to fail. 182 <!-- https://gcc.gnu.org/PR107855#c6 --> 183 Additionally, several tests in the 184 <filename class='directory'>vect</filename> directory are known to fail 185 if the hardware does not support AVX.</para> 174 <filename>contracts-tmpl-spec2.C</filename> are known to fail. 175 <!-- 176 It seems a regression in 13.2 but it does not happen in 177 https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/792164.html. 178 I'll investigate further. 179 --> 180 Some C++ module tests named <filename>xtreme-*</filename> are known to 181 fail. 182 </para> 183 184 <!-- Need further investigation --> 185 <para>Many gcc and g++ tests related to hwasan are known to fail.</para> 186 186 187 187 <para> … … 253 253 platform-specific differences in the dynamic linker name):</para> 254 254 255 <screen><computeroutput>[Requesting program interpreter: /lib 64/ld-linux-x86-64.so.2]</computeroutput></screen>255 <screen><computeroutput>[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]</computeroutput></screen> 256 256 257 257 <para>Now make sure that we're set up to use the correct start files:</para> … … 261 261 <para>The output of the last command should be:</para> 262 262 263 <screen><computeroutput>/usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded264 /usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded265 /usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>263 <screen><computeroutput>/usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded 264 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded 265 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen> 266 266 267 267 <para>Depending on your machine architecture, the above may differ slightly. … … 280 280 281 281 <screen><computeroutput>#include <...> search starts here: 282 /usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/include282 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/include 283 283 /usr/local/include 284 /usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/include-fixed284 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/include-fixed 285 285 /usr/include</computeroutput></screen> 286 286 … … 295 295 be ignored, but otherwise the output of the last command should be:</para> 296 296 297 <screen><computeroutput>SEARCH_DIR("/usr/ x86_64-pc-linux-gnu/lib64")297 <screen><computeroutput>SEARCH_DIR("/usr/aarch64-unknown-linux-gnu/lib64") 298 298 SEARCH_DIR("/usr/local/lib64") 299 299 SEARCH_DIR("/lib64") 300 300 SEARCH_DIR("/usr/lib64") 301 SEARCH_DIR("/usr/ x86_64-pc-linux-gnu/lib")301 SEARCH_DIR("/usr/aarch64-unknown-linux-gnu/lib") 302 302 SEARCH_DIR("/usr/local/lib") 303 303 SEARCH_DIR("/lib") 304 304 SEARCH_DIR("/usr/lib");</computeroutput></screen> 305 305 <!-- 306 306 <para>A 32-bit system may use a few other directories. For example, here 307 307 is the output from an i686 machine:</para> … … 315 315 SEARCH_DIR("/lib") 316 316 SEARCH_DIR("/usr/lib");</computeroutput></screen> 317 317 --> 318 318 <para>Next make sure that we're using the correct libc:</para> 319 319 … … 331 331 platform-specific differences in dynamic linker name):</para> 332 332 333 <screen><computeroutput>found ld-linux- x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen>333 <screen><computeroutput>found ld-linux-aarch64.so.1 at /usr/lib/ld-linux-aarch64.so.1</computeroutput></screen> 334 334 335 335 <para>If the output does not appear as shown above or is not received
Note:
See TracChangeset
for help on using the changeset viewer.