On Wed, Apr 11, 2018 at 8:55 AM, Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx> wrote: > No. > There is no problem to use a compiler without plugin support. > > If a user does not want to use plugin in the first place, > why does he/she need to be bothered by such information in stderr? So, I don't think it's needed for the first version of this, but it'd be nice to have a way for end users to discover _why_ some option they want is unavailable. Having them dig through the Kconfigs, edit scripts to see stderr again, running those by hand, etc, is really unfriendly. If, instead, stderr was visible from the menuconfig "help" for a Kconfig, it could serve as automatic documentation for why something wasn't enabled. I don't mean for stderr to get sprayed out during a regular "make"; I agree: that would be ugly and pointless. I'd just like some way for the reason behind an option being disabled to be discoverable in some way. -Kees -- Kees Cook Pixel Security -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
