On Thu, Dec 13, 2012 at 01:38:44AM +0100, Henrik /KaarPoSoft wrote: > So, it seems I need a multilib LFS. > [...] > > I have also looked a CLFS. > They build a couple of packages before binutils and then gcc. > But I cannot see any substantial differences in the gcc build itself... > > So: Any help / suggestions / info regarding LFS multilib would be most > appreciated! > > I am new to multilib, so I a wondering about stuff like: > - where in the toolchain building sequence should I target multilib? I > tried pass 1, but maybe it would be enough to target multilib later? > - what options should be used to configure the different packages at > each phase? > > Thanks in advance! > > /Henrik
Please take another look at clfs. The process is _longer_ than for LFS: 1. create cross-compile tools : this is where they build from x86_64 for both CLFS_TARGET="x86_64-unknown-linux-gnu" AND CLFS_TARGET32="i686-pc-linux-gnu". This also includes both 32- and 64-bit (e)glibc, 2. the rest of the temporary system. 3. chroot : first the test tools (tcl, expect, dejagnu) get built because those do not lend themselves to cross-compilation. 4. the final system now gets built. On x86_64, the general packages are built as 64-bit, which is fine, and *all* the libraries are built twice - first as 32-bit, then as 64. Say hello to --libdir, and note that LFS's symlinks for /lib64 and /usr/lib64 will NOT fit with this, and therefore if you build any 64-bit libraries from BLFS you will have to specify --libdir. Equally, you need to specify the 32-bit flags (-m32) if you want to build any 32-bit packages in BLFS. Short answer: you need both 32-bit and 64-bit toolchains, including libc. The clfs version works, but it is different from LFS. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
