On Monday 18 December 2006 13:39, Duncan wrote: > My point, however, was that since everything else I run is 64-bit, if > I didn't need the 32-bit tools to compile grub -- or if I was willing > to settle for the pre-compiled grub-static -- I could save myself a > *LOT* of extra work by simply using the no-multilib subprofile, thus > saving myself all that time compiling the 32-bit side of glibc and gcc > in particular.
I believe that lilo can be built in a 64-bit only environment (no-multilib). I use the no-multilib subprofile, and a few days ago, I found out that lilo was not masked (ie, "emerge -a lilo" did prompt me to install the package), so I suppose that it should work even in my 64-bit, no-multilib system. (However, I did not actually merge it, since grub-static still works fine here, so I can't be 100% sure). Looking at the changelog, it seems that my suppositions are correct: 06 Jan 2006; Olivier Crête <[EMAIL PROTECTED]> lilo-22.7.ebuild: Stable on amd64 So, it's been stable for almost a year now. Of course, this is not meant to be the start of another grub vs. lilo flamewar, but rather just a FYI. -- [email protected] mailing list
