> well, I still could reenable building gij-3.2 / gcj-3.2, if that's > necessary for the sarge release.
I don't have any reason to believe that this bug is new to gcj-3.3 - the only reason it wasn't spotted until now was kaffe+jython used to be broken for other reasons. So it's entirely possible that gcj-3.2 has it as well. As for the specific case that we hit, jython has already been updated to build using jikes instead (which circumvents the problem). So it's not urgent from jython's point of view. Kaffe's debug flags haven't yielded the magic answer I'm afraid. Ben.
