Hi, All. Thanks for all your feedback. It was nice learning about Hard links. I have put my response inline for Ken's point.
>>Message: 3 >>Date: Mon, 16 Jul 2012 16:18:51 +0100 >>From: Ken Moffat <[email protected]> >>Subject: Re: [lfs-support] LFS-BOOk-7.0:Section:5.2 Tool Chain Technical Notes: Doubt >>To: LFS Support List <[email protected]> >>Message-ID: <20120716151851.GA11324@milliways> >>Content-Type: text/plain; charset=utf-8 >>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. Emerson: I did some homework suggested above based on ls -i to get the inode numbers of the two directories. And found that the following files' inodes are matching in both the directories. */tools/bin/ ls -l -i (output is edited to show only the matching files)* 901167 -rwxr-xr-x. 4 lfs lfs 3947589 Jul 14 18:00 i686-lfs-linux-gnu-ld 901167 -rwxr-xr-x. 4 lfs lfs 3947589 Jul 14 18:00 i686-lfs-linux-gnu-ld.bfd 901154 -rwxr-xr-x. 2 lfs lfs 2955955 Jul 14 18:00 i686-lfs-linux-gnu-nm 901150 -rwxr-xr-x. 2 lfs lfs 3505170 Jul 14 18:00 i686-lfs-linux-gnu-objcopy 901146 -rwxr-xr-x. 2 lfs lfs 4067727 Jul 14 18:00 i686-lfs-linux-gnu-objdump 901149 -rwxr-xr-x. 2 lfs lfs 3055170 Jul 14 18:00 i686-lfs-linux-gnu-ranlib 901155 -rwxr-xr-x. 2 lfs lfs 3505165 Jul 14 18:00 i686-lfs-linux-gnu-strip */tools/$LFS_TGT/bin/ ls -l -i (output is edited to show only the matching files)* 901167 -rwxr-xr-x. 4 lfs lfs 3947589 Jul 14 18:00 ld 901167 -rwxr-xr-x. 4 lfs lfs 3947589 Jul 14 18:00 ld.bfd 901154 -rwxr-xr-x. 2 lfs lfs 2955955 Jul 14 18:00 nm 901150 -rwxr-xr-x. 2 lfs lfs 3505170 Jul 14 18:00 objcopy 901146 -rwxr-xr-x. 2 lfs lfs 4067727 Jul 14 18:00 objdump 901149 -rwxr-xr-x. 2 lfs lfs 3055170 Jul 14 18:00 ranlib 901155 -rwxr-xr-x. 2 lfs lfs 3505165 Jul 14 18:00 strip So as we discussed the hard links are created during the compilation process indeed. Thanks once again for the feedback. I have completed gcc-pass-2 successfully so far. >> If you are building a released version of the book, we think the >>commands are complete :) >>?en --
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
