Yep, I've read that, and I still believe it is wrong. It's not about the ls command, it's about the path of the target. Of course the command in the section 4.2 is right, as well as this one, but this one's target path is wrong.
In the 4.2 section, the command is: "ln -sv $LFS/tools /" That's a symbolic link with verbose output where "$LFS/tools" is the target of the link and "/" is where it's being put, so it's obviously all good. In this section, the command is: "ln -sv ../usr/bin/cpp /lib" That's again a symbolic link with verbose output where "../usr/bin/cpp" is the target of the link and "/lib" is where it's being put, but the error I'm reporting is that the target path is wrong. 2014-06-18 16:26 GMT+02:00 Matt Burgess <[email protected]>: > On 18/06/2014 15:18, Kazer Powa wrote: > >> http://www.linuxfromscratch.org/lfs/view/stable/chapter06/gcc.html >> >> The book says: >> "Some packages expect the C preprocessor to be installed in the /lib >> directory. To support those packages, create this symlink" >> And the command for this is: >> "ln -sv ../usr/bin/cpp /lib" >> But in that moment the user is in /sources/gcc-build, so that command is >> not going to work. I used this one instead, which I believe is the >> correct one: >> "ln -sv /usr/bin/cpp /lib" >> > > As the note in section 4.2 states: > > "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." > > Regards, > > Matt. > -- > http://lists.linuxfromscratch.org/listinfo/lfs-dev > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page >
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
