I've built LFS systems before, I started around 5.1.1.
Not VERY long ago, but I haven't used the 6.0 version.
I use a heavilly modified version, with many cutting edge versions. (including some CVS Bleeding Edge when I encounter certain problem)
I have an almost identical system to install it with 3 key differences:
Host "LFS" Sys
glibc-2.3.4-20040701
bash-2.05b
Not Stripped in any way
binutils 2.15.94.0.2
New "LFS" Sys
glibc-2.3.4 (stable!? - no longer CVS)
bash-3.0
binutils-2.15.96
I am trying things 1 step at a time, I will work with reinstalling the parts I stripped. With any luck that will produce great results, otherwise that points at 2 things: binutils-2.15.96 and glibc-2.3.4
Considering how many years they spend debugging until they call it stable, I cannot see this to be a glibc-2.3.4 problem. So if the stripping fails, then it better be the bleeding edge binutils...making me bleed
One if the issues I have had that points a finger at the linker (which if I am correct comes from glibc)
After building an identical SDL Version (1.2.8) on both systems the new system linker creates a new link that did not previously exist:
libSDL.so->libSDL-1.2.so.0.7.1
This causes the configure tests of all SDL programs to fail from confusion. Removing this link solves the problem inf the configure process; however, gcc ends up looking for this link and this link only when compiling from make on all of these programs, so I have to reattatch the link!
This issue did not exist on my host system