This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: gcj troubles
- From: Ray Auge <rayauge at doublebite dot com>
- To: gcj <java at gcc dot gnu dot org>
- Date: Sat, 24 Apr 2004 00:32:35 -0400
- Subject: Re: gcj troubles
- Organization: Doublebite
- References: <1082780681.1226.18.camel@localhost.localdomain>
- Reply-to: rayauge at doublebite dot com
On Sat, 2004-04-24 at 00:24 -0400, Ray Auge wrote:
> Hello All,
>
> Been having trouble compiling my app with gcj (gcj3.4.0, using xerces,
> xalan binaries from Fedora). Anyway, the make basically performs this
> sequence:
>
> PS: I'm using Java-Gnome (latest CVS). Also, this app works fine when run
> under Blackdown1.3.1 ('cept for many know bugs which are all my fault).
>
>
> for ALL the java files:
> /usr/bin/gcj34 -fPIC -fjni -Wall -g -O
> --classpath=/opt/gnome2/share/java-gnome/gtk2.4.jar:/opt/gnome2/share/java-gnome/gnome2.6.jar:\
> /opt/gnome2/share/java-gnome/glade2.6.jar:/usr/share/java/xercesImpl.jar:/usr/share/java/xmlParserAPIs.jar:\
> /usr/share/java/xalan.jar:/usr/share/java/gnu.regexp.jar:. -o build/last/util/ParseThread.o -c \
> last/util/ParseThread.java
>
> then for the final link:
> /usr/bin/gcj34 -fPIC -fjni -Wall -L/opt/gnome2/lib -lgtkjar2.4
> -lgnomejar2.6 -lgladejar2.6 -L/usr/lib -l-gnu.regexp-1.1.4
> -l-javax-xml-parsers-2.2.1 -l-org-apache-xerces-2.2.1
> -l-org-w3c-dom-2.2.1 -l-org-xml-sax-2.2.1 -l-javax-xml-transform-2.4.1
> -l-org-apache-xalan-2.4.1
> build/last/gui/ConfigTreeView.o
> ...<all the "o"s>
> build/last/util/ParseThread.o
> --main=last.gui.GUI -o build/lastgui
>
> I get this error when trying to run the executable:
> [com_@localhost build]$ ./lastgui -c mapConfig.xml
> could not create widget: java.lang.reflect.InvocationTargetException
> Trace/breakpoint trap
>
> But this works:
> [com_@localhost build]$ ./lastgui
> Last, 0.1.0
> Contact: Ray Auge <rayauge@doublebite.com>
> Usage: java last.gui.GUI [-h|-c <[/path/]configfile>]
>
> -c alternate config file, defaults
> to DOCUMENT_ROOT/mapConfig.xml
> -v print version
> -h print this message
>
> Any help is appreciated.
Must I build each .o based on it's deps independently?
I'm I wrong to assume that linking all the ".o"s together will allow
each class to find other imported classes that are linked in the .o?
>
>
> --
> Ray Auge <rayauge@doublebite.com>
> Doublebite
>
--
Ray Auge <rayauge@doublebite.com>
Doublebite