public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: ffileppo <ffileppo@libero.it>
Cc: java <java@gcc.gnu.org>
Subject: Re: gcj 4.4 and AWT toolkit
Date: Thu, 31 Jul 2008 11:55:00 -0000	[thread overview]
Message-ID: <4891A7FF.6020605@redhat.com> (raw)
In-Reply-To: <K4VCWP$4B9F3FBDA6DFAF4A38DD88B9545DC378@libero.it>

ffileppo wrote:
>> ffileppo wrote:
>>> Hi guys,
>>>
>>> I'm getting the following exception when I try to run AWT/SWING code using gcj 4.4 (which is using classpath 0.97.2). This is happening on both x86 and arm. It works fine using gcc 4.3
>>>
>>> Exception in thread "main" java.awt.AWTError: Cannot load AWT toolkit: gnu.java.awt.peer.gtk.GtkToolkit
>>>    at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:607)
>>>    at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:103)
>>>    at java.awt.Window.<init>(Window.java:133)
>>>    at java.awt.Frame.<init>(Frame.java:246)
>>>    at javax.swing.JFrame.<init>(JFrame.java:123)
>>>    at MainPanel.main(AWT)
>>> Caused by: java.lang.UnsatisfiedLinkError: initIDs
>>>    at gnu.java.awt.peer.gtk.GtkToolkit.initIDs(GtkToolkit.java:137)
>>>    at gnu.java.awt.peer.gtk.GtkToolkit.initializeGlobalIDs(GtkToolkit.java:168)
>>>    at gnu.java.awt.peer.gtk.GtkToolkit.<clinit>(GtkToolkit.java:183)
>>>    at java.lang.Class.initializeClass(natClass.cc:780)
>>>    at java.lang.Class.forName(Class.h:742)
>>>    at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:583)
>>>    ...5 more
>>>
>>> Any thoughts or idea?
>> You didn't build it?  --enable-java-awt=gtk  ?
>>
>> Andrew.
>>
> 
> Hi Andrew,
> 
> Yes, I've built AWT peer
> 
> My configure:
> 
> Configured with: ../configure --prefix=/media/disk/x86-gcc-inst --disable-libssp --disable-libgomp --disable-libmudflap --enable-libgcj --disable-bootstrap --disable-multilib --disable-sjlj-exceptions --enable-languages=c,c++,java --enable-java-awt=gtk
> 
> The problem seems to be that it can't find libgtkpeer.so, which is obviously present.
> 
> This is working as intended with gcc 4.3
> 
> Can anyone try to reproduce this problem?

Try running with LD_DEBUG=files.

Andrew.

  reply	other threads:[~2008-07-31 11:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 11:51 ffileppo
2008-07-31 11:55 ` Andrew Haley [this message]
2008-08-01 11:23 ` Mark Wielaard
  -- strict thread matches above, loose matches on Subject: below --
2008-08-14 16:59 ffileppo
2008-08-14 17:03 ` Andrew Haley
2008-08-17 21:45   ` Mark Wielaard
2008-08-18 18:38     ` Andrew John Hughes
2008-08-21 17:13       ` Tom Tromey
2008-08-22  0:49         ` Andrew John Hughes
2008-08-22  1:15           ` Tom Tromey
2008-08-29 23:21             ` Andrew John Hughes
2008-08-14 13:24 ffileppo
2008-08-13 15:43 ffileppo
2008-08-14 13:13 ` Mark Wielaard
2008-08-01 11:33 ffileppo
2008-07-31 18:21 ffileppo
2008-07-31 13:09 ffileppo
2008-07-31 14:30 ` Andrew Haley
2008-07-31 12:46 ffileppo
2008-07-31 12:51 ` Andrew Haley
2008-07-31 12:08 ffileppo
2008-07-31 12:17 ` Andrew Haley
2008-07-30 19:46 ffileppo
2008-07-31  8:40 ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4891A7FF.6020605@redhat.com \
    --to=aph@redhat.com \
    --cc=ffileppo@libero.it \
    --cc=java@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).