On Sun, May 08, 2005 at 08:20:50PM +0200, Sam Ravnborg wrote: > > Shouldn't kconfig exit with an error if a not available symbol gets > > selected? > No. There are meny configurations where we select a symbol that is > only visible in some configurations. > > Several possibilities exists: > 1) Silently ignore SELECT SYMBOL when SYMBOL is undefined > 2) Warn - as we do today > 3) Error out as you suggest > > Option 1) is preferable for 'make oldconfig' simply because target group > here do not care. But it would be nice to know when one do a typing > error in SELECT. So one *config target should continue to warn about it.
I disagree. Consider that some developers do not use anything other than "make oldconfig" so having this silently ignore stuff means that these folk never get the warnings. I myself fall into this category. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
