Changeset 0636f6c for final-system/common/binutils.xml

Timestamp:

Feb 21, 2006, 1:57:38 AM (18 years ago)

Author:

Jim Gifford <clfs@…>

Children:

4d6fcf9

Parents:

db38a36

Message:

r981@server (orig r979): jim | 2005-12-30 10:11:32 -0800

r1226@server: cstaub | 2005-12-30 08:35:37 -0800
Updated package deps, removed explanation of cross-compiling from final-system binutils, and removed note about GRUB's testsuite failure

File:

• final-system/common/binutils.xml (modified) (2 diffs)

final-system/common/binutils.xml

@@ -25 +25 @@
 
       <seglistitem>
-        <seg>Bash, Coreutils, Diffutils, GCC, Gettext,
-        Glibc, Grep, Make, Perl, Sed, and Texinfo</seg>
+        <seg>Bash, Coreutils, Diffutils, Expect, GCC, Gettext,
+        Glibc, Grep, Make, Patch, Perl, Sed, Tcl, and Texinfo</seg>
       </seglistitem>
     </segmentedlist>
@@ -79 +79 @@
     <para os="n">Normally, the tooldir (the directory where the executables
     will ultimately be located) is set to <filename
-    class="directory">$(exec_prefix)/$(target_alias)</filename>. For
-    example, i686 machines would expand that to <filename
-    class="directory">/usr/i686-pc-linux-gnu</filename>. Because this
+    class="directory">$(exec_prefix)/$(target_alias)</filename>. Because this
     is a custom system, this target-specific directory in <filename
-    class="directory">/usr</filename> is not required. <filename
-    class="directory">$(exec_prefix)/$(target_alias)</filename> would
-    be used if the system was used to cross-compile (for example,
-    compiling a package on an Intel machine that generates code that
-    can be executed on PowerPC machines).</para>
+    class="directory">/usr</filename> is not required.</para>
 
     <important os="o">