Hi, On Mon, Aug 1, 2011 at 12:40 PM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: > On Mon, 1 Aug 2011, Arnaud Lacombe wrote: > >> Moreover, this approach is deemed to fail. The current symbol >> namespace is tied to an arch, so whenever you do: >> >> arch/arm/Kconfig: >> config FOO >> bool >> >> config BAZ >> bool >> >> drivers/cpufreq/Kconfig >> config BAR >> depends on ARM && FOO >> select BAZ >> >> You will end up triggering the warning for every ARCH != ARM... > > You can keep a state for those symbols with regard to their level of > reference. Surely if ARM isn't true, BAZ is not "actively" referenced > in the end. > he :) we enter in compilers optimizations. As much as I agree with you, that might not be trivial to implement given the internal, ad-hoc, structure of kconfig. All of that would be useless if we had a single global namespace. - Arnaud -- 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
