There seems to be a problem with the dependancies for lilo. At some point in the compilation, it requires nasm, but the package isn't required in the dependancies (emerge --pretend lilo)
hi. im afraid unless you provide more information im going to have to close this as INVALID because the dependencies look fine to me, and i cant reproduce that. what version of portage are you using? look at the ebuild: DEPEND="virtual/glibc dev-lang/nasm >=sys-devel/bin86-0.15.5" root@gateway /usr/portage/sys-apps/sh-utils # emerge lilo -p These are the packages that I would merge, in order. Calculating dependencies ...done! [ebuild N ] dev-lang/nasm-0.98.34 [ebuild U ] sys-apps/lilo-22.3.3-r1 root@gateway /usr/portage/sys-apps/sh-utils # emerge --version Portage 2.0.38 so again, im tempted to close this as INVALID unless you have a very good reason as to why i shouldnt?
actuallay, I was talking about the lilo-22.3.3.ebuild ebuild. If you look at its dependancies, you'll see: DEPEND="virtual/glibc >=sys-devel/bin86-0.15.5" no nasm in there Same problem occurs with previous versions of lilo (although I don't know if nasm is required for those versions)
this should not be a problem anymore, lilo-22.3.3-r1 is the latest, unmasked, stable version to use. one of the devels checked in an old lilo recently, by mistake. if that one is still there, ignore it. guess he was smoking crack.
