After wrestling with the automake warnings, I decided I had some bigger fish to fry, and went after the gcc warnings. Using some nice autoconf machinery from the AC Archive I extended our configure script to add as many gcc warnings as I consider useful.

The reason for this is that kaffe seems to happily crash on so many platforms. So instead of chasing them all down with gdb, I decided to take a more indirect approach to debugging, and start fixing all the ugly, nasty hacks in our code first, before I even think about wielding the debugger on them.

Of course, the initial results are disappointing yet promising. Today I've only barely scratched the surface of the few thousand or so warnings to fix, but it's fun, in a laid back way. You look at code, try to figure out what the compiler means, and when you notice that the compiler's right, chuckle, and move on to the next fix.