problems in the boot phase

Jari Kankaala jarik at
Fri Jan 27 07:17:19 PST 2006

>   Either I'm missing your irony, or this is a new value of 'good' ;)
>   As far as I can see, you haven't told us what architecture you are
> building, but since grub is mentioned, I'll assume x86_64 (multilib).
>   On my pure64 (final) system I get
> ken at bluesbreaker ~ $ldd /sbin/agetty
> => /lib/ (0x00002b4ee9713000)
>          /lib/ (0x00002b4ee95fd000)
>   I guess that you should be seeing /tools/lib64/ at this stage in
> multilib.

Hi Ken,
you're quite right I'm building a x86_64 multilib. My host is the
lfslivecd-x86-6.2-pre2 which was the only one of the lfs cds I could
get to boot properly. It's my first cross-lfs and I guess there's
more than one thing I don't understand. The ldd was more of a naive
hope =). I figured out the problem. I was running a 32-bit version
of ldd and I couldn't run the one in /tools because I was running a
32-bit kernel (at least I think that's why). And yes, I feel really
stupid... Anyway, I tried again by booting a 64-bit Gentoo CD and
when I did my ldd's I got:

ldd /mnt/lfs/bin/login => /tools/lib64/ (0x00002aaaaabc6000) => /tools/lib64/ (0x00002aaaaacfb000) => /tools/lib64/ (0x00002aaaaae08000)
   /tools/lib64/ (0x00002aaaaaaab000)
ldd /mnt/lfs/sbin/agetty => /tools/lib64/ (0x00002aaaaabc6000) => /tools/lib64/ (0x00002aaaaacd4000)
   /tools/lib64/ (0x00002aaaaaaab000)
ldd /mnt/lfs/sbin/sulogin => /tools/lib64/ (0x00002aaaaabc6000) => /tools/lib64/ (0x00002aaaaacfb000) => /tools/lib64/ (0x00002aaaaae08000)
   /tools/lib64/ (0x00002aaaaaaab000)

Maybe it would be better to build the whole thing from the Gentoo
CD instead and chroot? I'd really like to understand what goes
wrong though. And thanks for your explaination of grub. Found some
info that indicated as much when I did the change to the menu.lst.

More information about the cross-lfs mailing list