Mohan (this-is-cool) 's snapshot gcc33-20030409

Andrew Haley
Tue May 13 20:18:00 GMT 2003

erik poupaert writes:
 > > gcc isn't #including the appropriate headers, probably because it
 > > doesn't have the right include path.
 > Part of the problem is related to the bug in mingw32/gcc that fails to
 > search gcc/bin/include for <jni.h>. It should be searched automatically.

Well, if the C++ compiler isn't searching for its own system headers
then it's totally broken.  I guess this needs to be fixed first.

I don't see what any of this has to do with gcj.


More information about the Java mailing list