From 28bb06349a8295a09322f70de6f72ca83282a168 Mon Sep 17 00:00:00 2001 From: Jeremy Huntwork Date: Mon, 30 Jan 2006 06:51:33 +0000 Subject: Various textual corrections. Thanks Chris Staub. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7317 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/binutils.xml | 29 +++++++++++++++++++---------- 1 file changed, 19 insertions(+), 10 deletions(-) (limited to 'chapter06/binutils.xml') diff --git a/chapter06/binutils.xml b/chapter06/binutils.xml index 7c25fe1f9..c5f7926b7 100644 --- a/chapter06/binutils.xml +++ b/chapter06/binutils.xml @@ -59,16 +59,25 @@ cd ../binutils-build make tooldir=/usr -Normally, the tooldir (the directory where the executables will ultimately -be located) is set to $(exec_prefix)/$(target_alias). For example, i686 -machines would expand that to /usr/i686-pc-linux-gnu. Because this is a custom -system, this target-specific directory in /usr is not required. $(exec_prefix)/$(target_alias) 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). + + The meaning of the make parameter: + + tooldir=/usr + + Normally, the tooldir (the directory where the executables will + ultimately be located) is set to $(exec_prefix)/$(target_alias). For + example, i686 machines would expand that to /usr/i686-pc-linux-gnu. Because this is + a custom system, this target-specific directory in /usr is not required. $(exec_prefix)/$(target_alias) 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). + + + The test suite for Binutils in this section is considered critical. Do not skip it under any -- cgit v1.2.3-54-g00ecf