On 12/5/19 12:33 AM, n952162 wrote:
The emerge should have checked for this and failed.
I don't think it should fail. I've routinely seen emerge check for various kernel / network / other parameters and issue warnings about things not being the way that the ebuild wants. But the ebuild does successfully emerge.
IMHO emerge / ebuild should not refuse to do what I tell it to do just because it doesn't like my custom kernel. The lack of kernel support is /my/ problem. The emerge / ebuild is capable of compiling perfectly fine without the kernel support. Perhaps I'm compiling on a fast machine that is running a different kernel and then copying the utilities to another system that does have the kernel support.
-- Grant. . . . unix || die -- Grant. . . . unix || die
