"Aaron M. Renn" <[EMAIL PROTECTED]> writes:

> I have started the coding spree I said I was going to go on.  I think
> java.io is ready for our first release.  I have made the following changes:
> 
> -- Fixed broken HTML in javadocs
> -- Updated for complete Java 1.2RC2 spec conformance (excepting
>    serialization (Geoff Berry's baby) and a couple items I felt 
>    absolutely had to be included despite non-conformance)
> -- Fixed a couple of bugs
> -- Re-ran all tests with the latest Japhar from CVS.  Everything ok.
> 
> Some things remain untested.  Nevertheless, all modules compile and the
> basics seem to be working alright.  Building things remains the big
> problem.  I am still compiling the Java by hand and the native code must be
> hand linked.
> 
> John, you said you were using my java.io for your testing, but I highly
> doubt that is the case.  The native library build succeeds fine, but due to
> a lack of interlibrary dependencies in libtool (possibly corrected now), it
> crashes on an undefined symbol at runtime.  Additionally, FileDescriptor had
> a bug that was exposed by the latest Japhar which caused JVM symbol lookup
> errors.
> 
> Another issue is that the native routines still use functions in John's JCL
> common library that I don't know if we still are officially using.  I'm
> talking the method/field id caching and JCL_jstring_to_cstring.

I think we need to nail down what we are using, JCL/NSA/others, and
document it in the hacking texinfo file.

> If anybody wants to test with java.io, let me know and I'll put up a tarball
> with compiled Java classes and instructions on how to build the native
> code.  (You need to link and install the native shared library by hand).

Could you change the appropriate Makefile.am's to have libtool do this
for you now?  This is supported on Linux with libtool... and I look at
it as a libtool bug/feature to be fixed on platforms it doesn't work
on just yet.  Since I don't know exactly what has to be done native
side to make this work I'm also not sure what other native libs,
etc. need this same work.

> Next up, I need to get java.net in shape, then I'm going to focus on either
> the build process or Japhar integration or whatever else needs help.

John should be posting a second, more usable patch, to the ftp site
soon.  He has also posted to the website information on getting
Classpath to work with a virtual machine in general.  This should be
helpful to anyone wanting to get us working with Kaffe.  Takers?

Brian
-- 
|-------------------------------|Software Engineer
|Brian Jones                    |[EMAIL PROTECTED]
|[EMAIL PROTECTED]                    |http://www.nortel.net
|http://www.classpath.org/      |------------------------------

Reply via email to