this actually seems to be directly related to the maverick binutils package, binutils_2.20.51.20100908-0ubuntu2_i386.deb
replacing lucid's binutils with this inside a chroot causes the same boot failures with CONFIG_RELOCATABLE=y, when used alongside the rest of lucid's toolchain.
this actually seems to be directly related to the maverick binutils package, binutils_ 2.20.51. 20100908- 0ubuntu2_ i386.deb
replacing lucid's binutils with this inside a chroot causes the same boot failures with CONFIG_ RELOCATABLE= y, when used alongside the rest of lucid's toolchain.
-matt