On Saturday, November 1, 2008 14:28:06 Ciaran McCreesh wrote: > On Sat, 1 Nov 2008 14:21:43 -0700 > > Gordon Malm <[EMAIL PROTECTED]> wrote: > > If you're compiling an out-of-tree module that requires the kernel be > > compiled with support for a particular item and the distccd host's > > kernel does not have that support compiles fail. Reference bug > > #120001 (though I know that it was properly diagnosed there). > > > > Then there's also this doozie. -> #167844. > > So far as I can see, when the correct options are passed to a build > system, the only issue is hardened being broken. There doesn't seem to > be any fundamental reason why distcc with a sane compiler can't be used > with kernel modules. If this is the case, wouldn't it be better to get > the hardened compiler fixed?
I use madwifi-ng extensively and have experienced the same issue with madwifi-ng as stated in that bug. For bug #167844, please read comment #13 and http://code.google.com/p/distcc/issues/detail?id=25. There's nothing to fix, hardened is doing the right thing as is distcc. The proper approach is to not distribute compiles of kernel modules. To not get too stuck on a single scenario, I think this would be a useful feature and desireable vs. the alternative of FEATURES=${FEATURES/distcc/}. This is not the first time its been requested, a simple search reveals bugs #28300, #80894. A quick grep shows these packages at minimum have to do some FEATURES checking and either pass a config option (if provided) or die "disable distcc and try again". dev-python/pyqwt media-gfx/sam2p media-tv/mythtv media-video/avidemux Gordon Malm (gengor)
