craig vanderborgh <[EMAIL PROTECTED]> writes:

> Hello,
>
> We are going to make a substantial attempt to get Derby running on GCJ.  The
> goal is not to run Derby on the GCJ "JVM", but instead to ahead-of-time 
> compile
> all the Derby sources (to .o files using the gcj compiler) so that the results
> are compact and fast enough to use on embedded systems.
>
> We plan on using GCJ 3.3.2, or perhaps 4.x.  What are the primary porting
> issues we're likely to encounter, and how do you think we ought to address 
> them
> in a way that might eventually be of use to the Derby project?

I haven't used GCJ myself. Does it support a mixed environment with
some byte-compiled code and some native code? If it doesn't, I guess
you will have trouble with the byte-code generation in the SQL
compiler.

-- 
Knut Anders

Reply via email to