Greg Schafer wrote: > The LFS/DIY build method is only meant to work on sane build hosts, ie: > pure 32, pure 64, etc. No multilib, no multi-arch, no bizarro crazy arse > setups. It's horses for courses dude. > You seem to be confused by the fact that I have reported two problems.
1) FSF binutils 2.17 don't recognize 64-bit libc.so.6 on Debian Lenny x86_64 (the issue is also reproducible on their weird x86 multilib setup, but let's forget this setup for now). I think that no debugging is needed further here - this is an obvious valid "downgrade" issue that can be resolved by using HJL binutils (but this is a bad solution, because it does nothing to prevent this problem from reappearing in the future). No multilib, no multi-arch, everything is simple. Please download this 75 MB tarball, unpack, chroot and see yourself (try to compile DIY x86_64 with binutils-2.17, gcc-4.1.2 and glibc-2.5.1): http://ums.usu.ru/~patrakov/test/lenny64-chroot.tar.bz2 2) Even after using HJL binutils, gcc fails to bootstrap on the weird multilib setup found in Debian Lenny x86 (note: this is not the same system as mentioned above as "Debian Lenny x86_64") with the gcc-4.1-bultilib package installed. This has been reported, you asked for debugging. I have not finished this debugging, but (judging from the failure in the non-bootstrap gcc build where I forgot to disable libmudflap - a mismatch in the number of bits in two declarations of a variable) it looks like a problem with the host headers that are not fully {64-bit,multilib}-ready. Here (but not in the first case) you may be right about FUD, "not-so-simple host" and the need for cross-compilation. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
