Thanks Godmar,
Now I see the problem here.
The classes in the java directory were taken from the Sun JDK1.2. The
reason for this was that they did not exist before in Kaffe. The
reason it fails in Kaffe is simply because it calls a native function
which doesn't exist in Kaffe. I didn't see this
Stefan,
this is the desired behavior.
For instance, if there is a directory ./java with say
./java/lang/Object.class, then I *want* Kaffe to load this
file for java.lang.Object and not the java/lang/object.class from
Klasses.jar. Although it can be confusing (the whole CLASSPATH idea
is ill-
Hi,
I've noticed that Kaffe behaves differently comparing to JDK in
respect to where the current directory ends up in the CLASSPATH. I happened to
have a directory in the current directory called java which contained
classes. This confused kaffe so much that it failed to
locate the standard Java
