This patch addresses the problem Per is seeing with Kawa.
The story is, we ought to be using the bootstrap class loader in these
places. However, existing code relies on us using the system class
loader. If we use the bootstrap loader, then a precompiled
application cannot use Class.forName() and expect it to find classes
from the classpath -- since the main class will have been loaded by
the bootstrap loader, which doesn't search the classpath.
On the trunk we will fix this more correctly, by providing a mechanism
to distinguish between linked-in classes which should be loaded by the
system loader, and classes in libgcj, which should be loaded by the
bootstrap loader.
I would like to check this in to 4.0.