This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCJ Swing/AWT working on OS X -- article


John Gabriele wrote:

Thanks for the reply Bryce.

Well, I've got gcc installed in /usr/local/gcc_cvs, and I had set
DYLD_LIBRARY_PATH to /usr/local/gcc_cvs/lib and had *not* set CLASSPATH,
so I think I was already doing what you suggest:


~/temp/gcj_stuff $ ls /usr/local/gcc_cvs/lib/lib*awt*
/usr/local/gcc_cvs/lib/lib-gnu-java-awt-peer-gtk.6.0.0.dylib* /usr/local/gcc_cvs/lib/lib-gnu-java-awt-peer-gtk.dylib@
/usr/local/gcc_cvs/lib/lib-gnu-java-awt-peer-gtk.6.dylib@ /usr/local/gcc_cvs/lib/lib-gnu-java-awt-peer-gtk.la*



~/temp/gcj_stuff $ echo $CLASSPATH




~/temp/gcj_stuff $ echo $DYLD_LIBRARY_PATH
/usr/local/gcc_cvs/lib


That looks right. I guess the libgcj shared-object dynamic loading mechanism isn't working on OS X, then. Maybe ltdl isn't working right.

How can I tell when I'm running natively compiled code vs. when I'm
running interpreted bytecode?


Unfortunately I don't know of an easy way. We plan to add new runtime debugging options to libgcj that should help when you need to diagnose things like this. Perhaps a runtime option to disable the interpreter, too.

Regards

Bryce


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]