On Mon, Jul 16, 2012 at 09:23:13AM -0500, Eleanore Boyd wrote: > On 7/16/2012 9:10 AM, Emerson Yesupatham wrote: > > > >"Binutils installs its assembler and linker in two locations, > >/tools/bin and /tools/$LFS_TGT/bin. The tools > >in one location are hard linked to the other." > >/tools/bin and /tools/$LFS_TGT/bin should be hard linked? I am not > >able to see any commands mentioned in the book to create a hard > >link between them. > >I am going to start gcc pass-2 compilation, so just wanted to know > >if any hard link needs to be created inside /tools/ to avoid any > >failures. > >Kindly explain if I miss something. > > > The compilation process creates the hard links, so there is no need > to manually create links. If anything, creating links beforehand may > cause errors due to the links pointing nowhere. > Correct. The links are NOT for the directories, they are just two names for programs. In general, hard links are used to give multiple names to a single binary, often with slightly different functionality (e.g. bzip2, bzcat). Here, they are used to put the alternative name in a different directory. Use ls -i to discover the inode numbers of the binutils programs in the two directories.
If you are building a released version of the book, we think the commands are complete :) ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
