public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: Which library implementation to use/work on?
Date: Tue, 13 Mar 2012 17:07:00 -0000	[thread overview]
Message-ID: <4F5F7ED5.4030905@redhat.com> (raw)
In-Reply-To: <CANEZrP0Fg5YUrGFBUiFBPgVTDAGZAz4LKCATdwfYMsSAb0Aq1A@mail.gmail.com>

On 03/13/2012 04:56 PM, Mike Hearn wrote:
> Hi there,
>
> I'm investigating GCJ for a project of mine to open up a Java library
> to the world of [Objective] C++ via the quite lovely CNI interface.
>
> My project depends on the Google protocol buffers library. Attempting
> to compile this jar reveals that there is a slight gap in
> java.util.regex in GNU Classpath.
>
> I'm trying to figure out what I should do with my time:
>
> 1) Write a patch to classpath - problem, project appears to be dead?
> 2) Try and somehow compile against Apache Harmony - problem, project
> also appears to be dead?
> 3) Change the protobufs library so it avoids the stubs in Classpath
>
> It seems that trying to support GCJ will keep my project at the level
> of Java 1.5 (or 1.4?) forever, as it's no longer being developed,
> which is a shame.
>
> I recall that some time ago Sun open sourced Java, but I don't know if
> it's compatible with what I want to do or how it plays together with
> GCJ (if at all).
>
> Any tips for what I should do?

I'd just fix up java.util.regex in Classpath as long as it wasn't
too hard.

Updating gcj to use the class library from Sun's now-free OpenJDK is
on my list of long-term projects.  It's a big job though, even for an
expert.

Andrew.

  reply	other threads:[~2012-03-13 17:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 16:57 Mike Hearn
2012-03-13 17:07 ` Andrew Haley [this message]
2012-03-13 18:26 ` Mike Hearn
2012-03-13 18:39   ` Andrew Haley
2012-03-14 10:40   ` Mike Hearn
2012-03-14 10:43     ` Chris Burdess
2012-03-14 11:11       ` Mike Hearn
2012-03-14 11:12         ` Andrew Haley
2012-03-14 12:14 ` Andrew Hughes
2012-03-14 12:17   ` Mike Hearn
2012-03-14 12:31     ` Andrew Hughes
2012-03-14 12:35       ` Mike Hearn
2012-03-14 18:32         ` Andrew Hughes
2012-03-15 12:24           ` Mike Hearn
2012-03-15 12:37             ` Andrew Hughes
2012-04-07 15:29               ` Mike Hearn
2012-04-07 18:28                 ` Bryce McKinlay
2012-04-08 13:18                   ` Mike Hearn
2012-04-10 15:53                     ` Mike Hearn
     [not found]                       ` <CANEZrP2ukT8zjNjma9yBREJ6wEuhdU6Qb=bPSOjemTYjzwrH5g@mail.gmail.com>
     [not found]                         ` <CANEZrP0QcpHjxKHWoi=A8+CcE2gPzm2_eO4_PG5=BmMHj-f_+Q@mail.gmail.com>
2012-05-30 21:14                           ` Mike Hearn

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=4F5F7ED5.4030905@redhat.com \
    --to=aph@redhat.com \
    --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).