1i5t5.duncan at cox
Sep 29, 2004, 1:24 AM
Post #4 of 12
Travis Tilley posted <415A490D.5070906 [at] gentoo>, excerpted below, on
Wed, 29 Sep 2004 01:33:01 -0400:
> also, with the new multilib stages i'm hoping to deprecate (but not get
> rid of) grub-static, since grub compiles just fine with a multilib gcc.
> grub-static will need to be kept around for non-multilib users, but it
> probably wont be touched unless there are critical bugs that need fixing.
Any chance of getting LILO working? I know it works on AMD64 (altho it
must be 32-bit, like GRUB), as I kept the Mandrake AMD64 version (which
was the exact same binary RPM as on their i586 product) when I switched,
and recently updated to the 32-bit binary from the LILO home page, after I
tried and failed to get the Gentoo ebuild to compile here, with multi-lib
Again, working LILO binaries work, so it should be /just/ a matter of
invoking the proper patch magic to get it compiling with multi-lib.
Unfortunately, that may be easier said than done. The errors when
attempting the compile here were definitely beyond my very limited
trouble-shooting abilities. (I don't claim to know C, tho I can and do
muddle thru enough of it to fix an occasional problem here or there, if
it's trivial enough.)
If I could get that working, my entire system, save for a single rather
old DOS game (Master of Orion original, (c) 1993, which I still play,
now using dosbox-cvs, which actually works in 64-bit mode, altho the
dosbox regular ebuild won't, tho it compiles.), would be Gentoo
from-source. I don't really want to build and keep updated an entire
32-bit chroot just so I can build LILO from time to time! Using the binary
from the LILO site works, but it's not quite the same as compiling it
myself, so I'd be a happy camper if Gentoo LILO could be made to emerge w/
Duncan - List replies preferred. No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
gentoo-amd64 [at] gentoo mailing list