public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Andrew John Hughes" <gnu_andrew@member.fsf.org>
To: "Mark Wielaard" <mark@klomp.org>
Cc: java <java@gcc.gnu.org>
Subject: Re: gcj 4.4 and AWT toolkit
Date: Mon, 18 Aug 2008 18:38:00 -0000	[thread overview]
Message-ID: <17c6771e0808181137j672e3d04m1b2ad6edd3aa8749@mail.gmail.com> (raw)
In-Reply-To: <1219009444.30922.16.camel@hermans.wildebeest.org>

On 17/08/2008, Mark Wielaard <mark@klomp.org> wrote:
> Hi,
>
>
>  On Thu, 2008-08-14 at 18:02 +0100, Andrew Haley wrote:
>  > >> Have to think about the cleanest way to solve this. But reverting this
>  > >> part of the import (attached) should get you going for now. You'll need
>  > >> to configure with --enable-java-maintainer-mode (see the libjava/HACKING
>  > >> file for more explanation).
>  >
>  > Thanks Mark.  We definitely need this fix in mainline gcj.
>
>
> I checked in a slightly simpler version marking the changes with GCJ
>  LOCAL. I hope to come up with a better/real solution in upstream
>  classpath (I really would like to just get rid of that whole
>  Configure.java.in file).
>
>  2008-08-17  Mark Wielaard  <mark@klomp.org>
>
>         * gnu/java/awt/peer/gtk/CairoGraphics2D.java: Always loadLibrary
>         gtk-peer.
>         * gnu/java/awt/peer/gtk/GdkFontPeer.java: Likewise.
>         * gnu/java/awt/peer/gtk/GdkPixbufDecoder.java: Likewise.
>         * gnu/java/awt/peer/gtk/GdkGraphicsEnvironment.java: Likewise.
>         * gnu/java/awt/peer/gtk/GtkToolkit.java: Likewise.
>         * gnu/java/awt/peer/gtk/GdkScreenGraphicsDevice.java: Likewise.
>         * gnu/java/awt/peer/gtk/*.class: Rebuilt.
>
>  Cheers,
>
>
>  Mark
>
>

On the subject of Configuration.java.in, can anyone explain why
running scripts/makemake.tcl on the 0.98 merge branch resulted in the
following?

-gnu/classpath/Configuration.java \
+classpath/gnu/classpath/Configuration.java \

Is this a mistake?

Thanks,
-- 
Andrew :-)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

  reply	other threads:[~2008-08-18 18:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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-31 11:51 ffileppo
2008-07-31 11:55 ` Andrew Haley
2008-08-01 11:23 ` Mark Wielaard
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=17c6771e0808181137j672e3d04m1b2ad6edd3aa8749@mail.gmail.com \
    --to=gnu_andrew@member.fsf.org \
    --cc=java@gcc.gnu.org \
    --cc=mark@klomp.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).