From 3022304849cf749b3a97e48e0683ae9eb3a76e40 Mon Sep 17 00:00:00 2001 From: Pierre Labastie Date: Sun, 21 Jun 2020 16:12:37 +0000 Subject: [PATCH] Remove an unneeded file git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11971 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter04/creatingtoolsdir.xml | 48 ---------------------------------- 1 file changed, 48 deletions(-) delete mode 100644 chapter04/creatingtoolsdir.xml diff --git a/chapter04/creatingtoolsdir.xml b/chapter04/creatingtoolsdir.xml deleted file mode 100644 index 0a42daa70..000000000 --- a/chapter04/creatingtoolsdir.xml +++ /dev/null @@ -1,48 +0,0 @@ - - - %general-entities; -]> - - - - - Creating the $LFS/tools Directory - - All programs compiled in - will be installed under $LFS/tools - to keep them separate from the programs compiled in . The programs compiled here are - temporary tools and will not be a part of the final LFS system. By keeping - these programs in a separate directory, they can easily be discarded later - after their use. This also prevents these programs from ending up in the - host production directories (easy to do by accident in ). - - Create the required directory by running the following as - root: - -mkdir -v $LFS/tools - - The next step is to create a /tools - symlink on the host system. This will point to the newly-created directory on - the LFS partition. Run this command as root as well: - -ln -sv $LFS/tools / - - - The above command is correct. The ln command - has a few syntactic variations, so be sure to check - info coreutils ln and ln(1) - before reporting what you may think is an error. - - - The created symlink enables the toolchain to be compiled so that it - always refers to /tools, meaning - that the compiler, assembler, and linker will work both in Chapter 5 - (when we are still using some tools from the host) and in the next (when - we are chrooted to the LFS partition). - -