+++ This bug was initially created as a clone of Bug #115383 +++ why did you guys close the former bug ? the problem is that genkernel stupidly demands a loadable / loaded "loop support" CONFIG_BLK_DEV_LOOP and only with that it seems to work I re-compiled my kernel several times for this: zcat /proc/config.gz | grep LOO CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_DM_LOOP is not set CONFIG_AUFS_BDEV_LOOP=y # CONFIG_VIRTIO_BALLOON is not set (I prefer to compile support in) so I'm politely asking to provide a fix for it or clarifying the error message in future genkernel versions that the following not so clear error message doesn't appear anymore: * The build-host kernel does not appear to have loop device support. * Please load loop support before running genkernel! * ERROR: Load loop support! * -- Grepping log... -- * The build-host kernel does not appear to have loop device support. * Please load loop support before running genkernel! * Gentoo Linux Genkernel; Version 3.4.10.904 * Running with options: --makeopts=-j20 --luks --disklabel --menuconfig all --kernname=test --no-clean * ERROR: Load loop support! * -- End log... -- * Please consult /var/log/genkernel.log for more information and any * errors that were reported above. * Report any genkernel bugs to bugs.gentoo.org and * assign your bug to genkernel@gentoo.org. Please include * as much information as you can in your bug report; attaching * /var/log/genkernel.log so that your issue can be dealt with effectively. * * Please do *not* report compilation failures as genkernel bugs! thanks !
Looking at the code, I can't find any reason for that check to even exist. Perhaps it's a misguided attempt to make sure the kernel that's being built has LOOP support. I think I'll just whack that code. This code has been removed in git.
(In reply to comment #1) > This code has been removed in git. Is this still an issue? If I do not hear anything in two weeks, I may close this bug.
(In reply to comment #2) > If I do not hear anything in two weeks, I may close this bug. Closing.
