Is this http://documents.jg555.com/multi-arch/x86 the guide on building 32 and 64 bit libraries for x86_64? I have been trying to build LFS for a while on my Athlon and have managed to go all the way to the end, bar being able to boot as I could not compile grub on my machine.

I would assume that multi-arch would mean so, but I do not see any difference between the way the packages are compiled in this document and the normal LFS book.

Thanks.

No, multi-arch != multilib.
I remember reading somewhere that x86_64-multilib is going to be one of the architectures supported by the multi-arch version of LFS, but as you can see by going a directory up (http://documents.jg555.com/multi-arch/), it is not available yet.
You have ended up with x86_64 system without 32-bit support.
Grub does not support x86_64. Lilo works fine.

Thanks for the reply. Could you please explain the difference between multi-arch and multilib?

I did compile lilo, but had problems booting it. I kept getting this silly L 01 01 01 01 error or L 09 09 09 09, no matter what I did, or no matter how much I edited /etc/lilo.conf or /etc/fstab on the LFS system.

The main problem with LILO, was trying to run the LILO command from within the chroot. I could neither run it or run fdisk on the hard disk carrying the LFS System. I guess the system protects from changing hard drive settings or writing to the MBR from within a chroot. I also tried copying /mnt/LFS/etc/lilo.conf to my system's /etc/lilo.conf, changing the name of the kernel to use from /boot/lfskernelimage to /mnt/LFS/boot/lfskernelimage, running LILO from the host to write the MBR, but keeping the file on the LFS system without any references to /mnt/LFS, but that did not work.

I then made a link from /boot/lfskernelimage to /mnt/LFS/boot/lfskernelimage and making lilo.conf on both the host and LFS system to look identical and running LILO from the host, but that did not work either!

I was so close and yet so far

Hello all,

Does anyone have an answer to the question above?

Thanks.

The system doesn't protect against changing the MBR in a chroot environment, otherwise the LFS book wouldn't work. Did you make sure to disable CFLAGS or any other optimizing flags when you compiled LILO? Posting the configuration files may help as well.

I compiled without any flags. My system is a suse 9.3 running on a sata hard disk. I am building my LFS system on hdd.

FROM WITHIN THE CHROOT:
This is my lilo.conf file:
boot=/dev/hdd

image=/boot/lfskernel-2.6.9
label=LFS
root=/dev/hdd1
read-write

running lilo produces:
mediacentre:/ # lilo
Fatal: raid_setup: stat("/dev/hdd")

running fdisk -l /dev/hdd and fdisk /dev/hdd produces:
mediacentre:/ # fdisk -l /dev/hdd
mediacentre:/ # fdisk /dev/hdd

Unable to open /dev/hdd

FROM WITHIN THE HOST SYSTEM:
mediacentre:/ # fdisk -l /dev/hdd

Disk /dev/hdd: 20.0 GB, 20020396032 bytes
16 heads, 63 sectors/track, 38792 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot Start End Blocks Id System
/dev/hdd1 * 1 389 196024+ 83 Linux
/dev/hdd2 390 1649 635040 82 Linux swap / Solaris
/dev/hdd3 1650 38792 18720072 83 Linux

Thanks.

Did you run the command (i.e. /sbin/udevstart) to fill your /dev directory?

Crap!! I don't believe that I did not check this!!!

OK, so /dev is empty bar /dev/pts, /dev/shm and /dev/null. Running udevstart does nothing as my /sys directory is empty. Not sure how that happenned. I will review the book and see where that is populated.

Thank a hundred million times

Got it!! Thank you so very very much

The problem was not running this before rentering the chroot:
mount -t proc proc $LFS/proc
mount -t sysfs sysfs $LFS/sys

Running this, chrooting, and then running udevstart was the fix.

Thank you very much again.