Changeset 460f575 for chapter08/binutils.xml
- Timestamp:
- 02/25/2022 08:47:36 PM (2 years ago)
- Branches:
- arm
- Children:
- 9c0b35a
- Parents:
- b0a6b0c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/binutils.xml
rb0a6b0c r460f575 72 72 find -name \*.1 -delete</userinput></screen> 73 73 --> 74 75 <para> 76 Now make a fix identified upstream that affects building some packages: 77 </para> 78 79 <screen><userinput remap="pre">sed -e '/R_386_TLS_LE /i \ || (TYPE) == R_386_TLS_IE \\' \ 80 -i ./bfd/elfxx-x86.h</userinput></screen> 81 74 <!-- 75 <para>Now remove one test that prevents the tests from running 76 to completion:</para> 77 78 <screen><userinput remap="pre">sed -i '/@\tincremental_copy/d' gold/testsuite/Makefile.in</userinput></screen> 79 --> 82 80 <para>The Binutils documentation recommends building Binutils 83 81 in a dedicated build directory:</para> … … 153 151 ultimately be located) is set to <filename 154 152 class="directory">$(exec_prefix)/$(target_alias)</filename>. For 155 example, x86_64 machines would expand that to <filename156 class="directory">/usr/x86_64-pc-linux-gnu</filename>. Because this is 157 153 example, aarch64 machines would expand that to <filename 154 class="directory">/usr/aarch64-unknown-linux-gnu</filename>. Because 155 this is a custom system, this target-specific directory in <filename 158 156 class="directory">/usr</filename> is not required. <filename 159 157 class="directory">$(exec_prefix)/$(target_alias)</filename> would be
Note:
See TracChangeset
for help on using the changeset viewer.