This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Patch: FYI: Get xlib peers working again - OK for branch-4.0?
- From: Tom Tromey <tromey at redhat dot com>
- To: "Scott Gilbertson" <scottg at mantatest dot com>
- Cc: <java-patches at gcc dot gnu dot org>
- Date: 18 Jul 2005 11:53:07 -0600
- Subject: Re: Patch: FYI: Get xlib peers working again - OK for branch-4.0?
- References: <166c01c5895a$c7eb0f60$3c16a8c0@mantatest.com>
- Reply-to: tromey at redhat dot com
>>>>> "Scott" == Scott Gilbertson <scottg@mantatest.com> writes:
Scott> I just checked in these changes to trunk. The xlib peers had
Scott> been busted for a long time, and these changes get them working
Scott> at least as well as they did a year ago (using my large
Scott> application for testing).
Unfortunately I just broke them again with the big classpath merge.
As I recall the problem is that ClasspathToolkit now declares some
abstract methods that the xlib peers do not implement. You can turn
on building them again pretty easily: remove the gnu/awt/xlib and
gnu/gcj/xlib lines from libjava/standard.omit, run makemake.tcl
(redirect stdout to sources.am), and run automake.
Scott> OK to commit the equivalent patch to branch-4.0?
Do the peers compile or work at all in 4.0?
Our rule thus far for 4.0.x has been that we won't break the C++
ABI. That is a pretty strict rule.
Tom