This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
Re: libgcj/6757: default AWT toolkit does not exist
- From: tromey at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, goran at kirra dot net, java-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tromey at gcc dot gnu dot org
- Date: 3 May 2003 01:39:39 -0000
- Subject: Re: libgcj/6757: default AWT toolkit does not exist
- Reply-to: tromey at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, goran at kirra dot net, java-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tromey at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: default AWT toolkit does not exist
Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Sat May 3 01:39:39 2003
Responsible-Changed-Why:
I'm handling this
State-Changed-From-To: open->closed
State-Changed-By: tromey
State-Changed-When: Sat May 3 01:39:39 2003
State-Changed-Why:
On the trunk we have Gtk peers which are enabled if
you configure correctly. So on some systems, at least,
this will no longer happen.
On other systems this will depend on someone writing
peers. There's no point in keeping a PR around for that
circumstance.
This fix will appear in 3.4 (or whatever we call the
next release coming off the trunk).
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6757