It took me a while to spot this message, and ignore the "clear_choices"
error reported by wish. At the end is a small patch so that xconfig
exits with a non-zero exit status, so that make aborts correctly.
I haven't been able to work out why the "Ooops" is generated in the
first place, but I have been able to track down that it is due to the
following in arch/i386/config.in (processor derived options).
if [ "$CONFIG_M386" != "n" ]; then
After that point, my lack of knowledge of xconfig's internals kicks in!
--- scripts/tkcond.c-dist Thu Dec 31 18:53:03 1998
+++ scripts/tkcond.c Fri Jan 1 11:27:52 1999
@@ -133,7 +133,7 @@
else
{
fprintf(stderr,"Ooops\n");
- exit(0);
+ exit(1);
}
}
-- `O O' | Home: Nick.Holloway@alfie.demon.co.uk http://www.alfie.demon.co.uk/ // ^ \\ | Work: Nick.Holloway@parallax.co.uk- 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/