- Timestamp:
- 05/13/2024 04:01:59 PM (4 months ago)
- Branches:
- xry111/arm64
- Children:
- c6e4dba
- Parents:
- f6548ac (diff), 5ff2f2e4 (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. - Location:
- chapter08
- Files:
-
- 7 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/automake.xml
rf6548ac r161a267 63 63 logical cores you want to use if you don't want to use all.</para> 64 64 65 <para>The test t/subobj.sh is known to fail.</para> 65 <para>Out of 2926 tests, 52 are known to fail due to incompatibilities in the 66 test scripts with gcc-14.1 or later.</para> 66 67 67 68 <para>Install the package:</para> -
chapter08/bash.xml
rf6548ac r161a267 50 50 --without-bash-malloc \ 51 51 --with-installed-readline \ 52 bash_cv_strtold_broken=no \ 52 53 --docdir=/usr/share/doc/bash-&bash-version;</userinput></screen> 53 54 -
chapter08/coreutils.xml
rf6548ac r161a267 128 128 environment):</para> 129 129 130 <screen><userinput remap="test">su tester -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check" < /dev/null</userinput></screen> 130 <screen><userinput remap="test">su tester -c "PATH=$PATH make -k RUN_EXPENSIVE_TESTS=yes check" \ 131 < /dev/null</userinput></screen> 131 132 132 133 <para>Remove the temporary group:</para> -
chapter08/expect.xml
rf6548ac r161a267 73 73 <screen><userinput remap="pre">tar -C tclconfig -xf ../autoconf-&autoconf-version;.tar.xz --strip-components=2 \ 74 74 autoconf-&autoconf-version;/build-aux/config.{guess,sub}</userinput></screen> 75 76 <para>Now, make some changes to allow the package with gcc-14.1 or later:</para> 77 78 <screen><userinput remap="pre">patch -Np1 -i ../expect-&expect-version;-gcc14-1.patch</userinput></screen> 75 79 76 80 <para>Prepare Expect for compilation:</para> -
chapter08/gcc.xml
rf6548ac r161a267 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>On ARM64 hosts, set the default directory name for 58 45 64-bit libraries to <quote>lib</quote>:</para> … … 73 60 --enable-default-pie \ 74 61 --enable-default-ssp \ 62 --enable-host-pie \ 75 63 --disable-multilib \ 76 64 --disable-bootstrap \ … … 144 132 important, but it takes a long time. First-time builders are 145 133 encouraged to run the test suite. The time to run the tests can be 146 reduced significantly by adding -jx to the <command>make -k check</command> command below,147 where x is the number of CPU cores on your system.</para>134 reduced significantly by adding -jx to the <command>make -k check</command> 135 command below, where x is the number of CPU cores on your system.</para> 148 136 </important> 149 137 … … 152 140 153 141 <screen><userinput remap="test">ulimit -s 32768</userinput></screen> 142 143 <para>Now remove/fix several known test failures:</para> 144 145 <screen><userinput remap="test">sed -e '/cpython/d' -i ../gcc/testsuite/gcc.dg/plugin/plugin.exp 146 sed -e 's/no-pic /&-no-pie /' -i ../gcc/testsuite/gcc.target/i386/pr113689-1.c 147 sed -e 's/300000/(1|300000)/' -i ../libgomp/testsuite/libgomp.c-c++-common/pr109062.c 148 sed -e 's/{ target nonpic } //' \ 149 -e '/GOTPCREL/d' -i ../gcc/testsuite/gcc.target/i386/fentryname3.c</userinput></screen> 154 150 155 151 <para>Test the results as a non-privileged user, but do not stop at errors:</para> … … 168 164 url="&test-results;"/> and 169 165 <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> 170 166 <!-- 171 167 <para> 172 In gcc tests (out of over 185,000), 173 seven tests in the <filename class='directory'>analyzer</filename> 168 Eight gcc tests (out of over 185,000): 169 <!- - https://gcc.gnu.org/PR106375 - -><filename>pr56837.c</filename> 170 and seven tests in the <filename class='directory'>analyzer</filename> 174 171 directory are known to fail. 175 172 176 <!- - https://gcc.gnu.org/PR109353 -->173 <!- - https://gcc.gnu.org/PR109353 - -> 177 174 One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is 178 175 known to fail. 179 176 180 For g++, 2 2tests (out of approximately 250,000): 14177 For g++, 21 tests (out of approximately 250,000): 14 181 178 <quote>AddressSanitizer*</quote> 182 tests, 7 <filename>interception-malloc-test-1.C</filename> tests, 183 and one test named <filename>contracts-tmpl-spec2.C</filename> are 179 tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are 184 180 known to fail. 185 181 186 On ARM64, many tests in the 182 Additionally, several tests in the 183 <filename class='directory'>vect</filename> directory are known to fail 184 if the hardware does not support AVX.</para> 185 --> 186 187 <para>On ARM64, many tests in the 187 188 <filename class='directory'>c-c++-common/hwasan</filename> 188 189 directory are known to fail in both gcc and g++ tests<!-- why? -->, … … 190 191 <!-- https://gcc.gnu.org/PR111124 --> 191 192 <filename class='directory'>g++.dg/modules</filename> 192 directory are known to fail in g++ tests. 193 </para> 194 195 <para>A few unexpected failures cannot always be avoided.The GCC developers196 are usually aware of these issues, but have not resolved them yet. 193 directory are known to fail in g++ tests.</para> 194 195 <para>A few unexpected failures cannot always be avoided. In some cases 196 test failures depend on the specific hardware of the system.<!--The GCC developers 197 are usually aware of these issues, but have not resolved them yet.--> 197 198 Unless the test results are vastly different from those at the above URL, 198 199 it is safe to continue.</para> -
chapter08/grub.xml
rf6548ac r161a267 54 54 <para> 55 55 If your system has UEFI support and you wish to boot LFS with UEFI, 56 you can skip this package in LFS, 57 and install GRUB with UEFI support (and its dependencies) by following 58 the instructions on 59 <ulink url="&blfs-book;postlfs/grub-efi.html">the BLFS page</ulink> 60 (with <parameter>--target=x86_64</parameter> removed). 56 you need to install GRUB with UEFI support (and its dependencies) by 57 following the instructions on 58 <ulink url="&blfs-book;postlfs/grub-efi.html">the BLFS page</ulink>. 59 You may skip this package, or install this package and the BLFS 60 GRUB for UEFI package without conflict (the BLFS page provides 61 instructions for both cases). 61 62 </para> 62 63 </note> -
chapter08/inetutils.xml
rf6548ac r161a267 40 40 <sect2 role="installation"> 41 41 <title>Installation of Inetutils</title> 42 43 <para>First, make the package build with gcc-14.1 or later::</para> 44 45 <screen><userinput remap="pre">sed -i 's/def HAVE_TERMCAP_TGETENT/ 1/' telnet/telnet.c</userinput></screen> 42 46 43 47 <para>Prepare Inetutils for compilation:</para>
Note:
See TracChangeset
for help on using the changeset viewer.