On Fri, Feb 03, 2012 at 01:29:09PM -0800, H. Peter Anvin wrote: > It seems relatively straightforward to do if we were to manifest some > CONFIG_ variables based on the target toolchain, e.g. > > CONFIG_GCC=0x040601 > > ... and perhaps do other tests. I suspect we would run the tests less > frequently than what we do right now with the tests embedded in the > Makefile. > > Does anyone have a feel for if this would be a good addition, and if so > where it best fits into the chain? This seems like a *great* idea. Unfortunately, a quick look at the implementation of kbuild suggests that it doesn't currently implement numeric comparisons (<, <=, >, >=), only equality (= and !=). Most of the time, a Kconfig file will want to write "depends GCC >= some_version". Looking at scripts/kconfig/expr.c, it doesn't look that hard to add, though. - Josh Triplett -- 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
