On Sunday 24 September 2006 17:46, Joe Ciccone wrote: > The first pass of binuntils is to provide the tools for your target > architecture that build into /tools. The first pass of glibc is static > so it does not go looking for the glibc startfiles (Which don't exist > yet). Then you build glibc into /tools providing the startfiles, > ld-linux.so.2, libc.so, and a bunch of other libs. Then you can build a > gcc with --enable-shared so that you have a cross-compiler that creates > dynamically linked executables against the glibc you built after the > first pass of gcc. Binutils is only needed to be built once because > you're not changing the search path at all. In LFS, You go from linking > to the host to after adjusting the toolchain linking to /tools. In CLFS, > you're toolchain is setup to link against /tools from the start. That is > why there is no adjusting the toolchain cross-tools or tools.
Thanks for the explanation! Why not to add the explanation to the book? It will help understanding of what a CLFS-builder is doing that's always good. -- Nothing but perfection pv _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
