Linking problems with Kaffe VM

[Peter Eisentraut]

I'm attempting to create some sort of a Java plugin for an existing
application.  Conceptually it looks like:

    application -> glue.so -> kaffe

where I'm writing glue.so, which will be dlopen'ed by the application.  
Works okay after I spent days figuring out the correct JavaVMInitArgs
settings.

Now when I call JNI_CreateJavaVM(), Kaffe somewhere deep down calls a
translate() function.  That function already exists in the main
application, and that's the version that gets called.  Crash and burn
results.

Okay, so I could rename my own translate() function, possibly only to
discover the next conflict.  What I'm thinking was that

(a) Kaffe should keep its namespace clean

(b) On ELF systems ISTM that you could link Kaffe with -Bsymbolic.  This
is not infinitely portable though.  (Maybe something for libtool?)  Also,
since Kaffe 1.0.6 doesn't build on RH 7.0, I can't even begin to test this
now.

Any thoughts?

-- 
Peter Eisentraut      peter_e at gmx.net       http://yi.org/peter-e/