On Wed, 29 Jul 2009 01:29:31 -0800, Rabbit <rabbit8...@gmail.com> wrote:
> but I think we should use just only use i686-pc-linux-gnu > because I think it doesn't make sense to use i686-pc-lfs-gnu. The 'i686-lfs-linux-gnu' came in through the move across to DIY's build method [0]. This is described at [1]: "It is vitally important to ensure that the vendor field of the target triplet is something other than "pc" or "unknown". This is because we want to force the pass 1 toolchain into cross compilation mode. For example, if your real target is i686-pc-linux-gnu, set [$LFS_TGT] to i686-[lfs]-linux-gnu or even i686-FAKE-linux-gnu." In our chapter 5 toolchain notes this is summarised in: "Slightly adjusting the name of the working platform ensures that the first build of Binutils and GCC produces a compatible cross-linker and cross-compiler. Instead of producing binaries for another architecture, the cross-linker and cross-compiler will produce binaries compatible with the current hardware." A reference to LFS_TGT in the above paragraph would certainly clarify what's going on for me and help in understanding how this all hangs together. Regards, Matt [0] http://wiki.linuxfromscratch.org/lfs/changeset/8755/trunk/BOOK/chapter04/settingenviron.xml [1] http://refbuild.diy-linux.org/getting-started.html#environment -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
