Hi, On Tue, May 31, 2011 at 11:48 AM, David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote: > On Mon, 2011-05-30 at 20:24 -0400, Arnaud Lacombe wrote: >> It would seem that the underlying symbol is not visible, triggering >> the failure of sym_set_tristate_value(). > > Yes, this only lets you set *visible* symbols. If the symbol you're > interested in is not visible because some of its dependencies are not > set, it doesn't go and automatically enable those. > As for this choice, it *is* visible. You are missing a call to `sym_calc_value()' (actually sym_calc_visibility() but it is not exported) before the conditional to correct the visibility. Beside that, if the environment is to influence the configuration unconditionally, it would rather be better to do that when the Kconfig are parsed. - Arnaud > -- > David Woodhouse Open Source Technology Centre > David.Woodhouse@xxxxxxxxx Intel Corporation > > -- 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
