I finally got java to build with gtk support, but every program that I try to run fails like this simple example from a java book (pango is finding a null pointer) - [dranta:java/CHAPCODE/Ch12] dir% gcj -bind_at_load --main=Application -o Application Application.java [dranta:java/CHAPCODE/Ch12] dir% Application (.:18349): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed java.lang.InternalError: Pango: pango_color_parse: assertion `spec != NULL' failed <<No stacktrace available>> -:2: Invalid color constant '(null)' -:2: error: invalid string constant "#eee1b3", expected valid string constant Gtk-ERROR **: file gtkcontainer.c: line 2000 (_gtk_container_focus_sort): should not be reached aborting... java.lang.InternalError: Gtk: file gtkcontainer.c: line 2000 (_gtk_container_focus_sort): should not be reached <<No stacktrace available>> Abort [dranta:java/CHAPCODE/Ch12] dir% cat Application.java import java.awt.Frame; import java.awt.Color; import java.awt.event.WindowEvent; import java.awt.event.WindowAdapter; public class Application { public static void main (String args[]) { Frame myWindow = new Frame ("Window !"); myWindow.setBackground(Color.blue); myWindow.setSize(300,300); myWindow.setVisible(true); myWindow.addWindowListener (new WindowAdapter() { public void windowClosing (WindowEvent e) { System.exit(0); } }); } } [dranta:java/CHAPCODE/Ch12] dir% gcj --v Using built-in specs. Reading specs from /usr/local/java/lib/gcc/powerpc-apple-darwin8.7.0/4.2.0/../../../libgcj.spec rename spec startfile to startfileorig rename spec lib to liborig Target: powerpc-apple-darwin8.7.0 Configured with: ../gcc/configure --prefix=/usr/local/java --enable-languages=c,c++,java --enable-java-awt=gtk --enable-gtk-cairo --disable-multilib --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib Thread model: posix gcc version 4.2.0 20061016 (experimental)
*** Bug 29492 has been marked as a duplicate of this bug. ***
This turned out to be a gtk bug - a rebuild of glib-2.12.4 followed by a rebuild of gtk+-2.10.6 fixed the problem.
Closing as invalid then.