*This* problem (same config option available for different architectures)
does not exist in the current (newest 2.3.18-ac) version of xconfig parser...
However, the
if [ "$CONFIG_VAR_1" = "y" ]; then
bool 'Some option' CONFIG_VAR_2
else
tristate 'Some option' CONFIG_VAR_2
fi
is still a problem caused by the initial xconfig design
(of course only if CONFIG_VAR_1 *can* be defined).
Modifying this design seems not to be worth required work if a tool
replacing xconfig can be available soon (mconfig).
-- ======================================================================= Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl phone (48)(58) 347 14 61 Faculty of Applied Phys. & Math., Technical University of Gdansk- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/