On 08/14/2012 08:27 AM, Alex Williamson wrote: >> > >> > Do we need this level of control? Open question I'm just wondering every >> > time a new feature gets added together with --disable/--enable >> > switches. >> >> I don't think so--it's easy enough for an administrator to disable vfio >> for a user. > > Ok, out voted. I'll remove. Thanks, > There is an advantage to --enable-blah in that it errors out if build requirements are not satisfied, compared to silently disabling the feature with a plain ./configure. This is important for distro builds which can start to silently break features when we add a new build requirement. But it can be done later, possibly with a new --enable=vfio,kvm,... list instead of individual features. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
