I am working on my project and now that you mention it I think i agree with you. but there should be a reason for it.
Maybe someone more experienced would clarify this for us. On Mon, Jul 20, 2009 at 3:54 AM, booleandomain <[email protected]>wrote: > I don't fully understand the build method for LFS. > > I know the general idea is to first create a working minimal system > inside of ${LFS}/tools, chroot into ${LFS}, then use the programs inside > of /tools for building the final system. > > What I can't understand is: > > 1) Why editing gcc specs file instead of adding > -Wl,--dynamic-linker,/tools/lib/ld-linux.so.2? It seems to me an > equivalent but more elegant way of accomplishing the same thing, that is > making sure everything you install in /tools get not linked to the > host's dynamic linker but to the dynamic linker inside of /tools. > > 2) Why two passes for gcc and binutils in chapter 5? I think one pass > should be enough, just after glibc installation. > > 3) Why playing with ld, ld-new and ld-old? I can't get it. > > I'm aware the book explains everything, but I think I need different > words in order to understand. > > Thanks. > > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > Unsubscribe: See the above information page > -- ====================================================================== "The shortest way to do many things is to do only one thing at a time."
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
