public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Per Bothner <per@bothner.com>,
	       Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: "classpath@gnu.org" <classpath@gnu.org>,
	       "java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: Re: GCJ ------ file type not supported by system
Date: Thu, 04 Sep 2014 08:14:00 -0000	[thread overview]
Message-ID: <54081F39.5020205@redhat.com> (raw)
In-Reply-To: <540756E6.4000804@bothner.com>

On 03/09/14 18:59, Per Bothner wrote:
> On 09/03/2014 09:35 AM, Guillermo Rodriguez Garcia wrote:
>> What would you like me to do? How can I help ?
> 
> More useful than updating Classoath per se would be creating
> a version of GCJ that uses OpenJDK's javac for compiling to bytecodes,

Why?  Eclipse's javac seems fine.

> (I don't believe Eclipse's compiler is as solid or complete, though that may be
> my bias from having worked with javac engineers.  It's probably good enough for
> at least the initial stages of merging in OpenJDK classes.)

Oh, OK.  Most of the world I know about uses Eclipse for everything.

Andrew.


  parent reply	other threads:[~2014-09-04  8:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  8:00 kgy
2014-08-29  8:07 ` Fwd: " Andrew Haley
2014-08-29  8:34   ` Mario Torre
2014-08-29  9:47   ` Guillermo Rodriguez Garcia
2014-08-29  9:57     ` Mario Torre
2014-08-29 10:00       ` Guillermo Rodriguez Garcia
2014-09-01  9:03         ` Andrew Haley
2014-09-01  9:32           ` Guillermo Rodriguez Garcia
2014-09-01 10:47             ` Mario Torre
2014-09-03 16:12               ` Guillermo Rodriguez Garcia
2014-09-03 16:30                 ` Andrew Haley
2014-09-03 16:35                   ` Guillermo Rodriguez Garcia
2014-09-03 17:11                     ` Andrew Haley
2014-09-03 17:31                       ` Guillermo Rodriguez Garcia
2014-09-03 18:00                         ` Mark Wielaard
2014-09-03 19:00                           ` Guillermo Rodriguez Garcia
2014-09-03 17:59                     ` Per Bothner
2014-09-03 18:06                       ` Mark Wielaard
2014-09-04  8:14                       ` Andrew Haley [this message]
2014-09-04 20:37                         ` Per Bothner
2014-09-04 12:14                 ` Andïï
2014-09-04 16:17                   ` Guillermo Rodriguez
2014-09-04 18:54                     ` Pekka Enberg
     [not found]                       ` <CABDcavbXxFiqTenZm0DJ8MhT5TLOgiMDhGArRjB5wpuTzG7c-g@mail.gmail.com>
2014-09-04 20:07                         ` Pekka Enberg
2014-09-04 20:15                           ` Andrew Haley
2014-09-04 20:43                             ` Pekka Enberg
2014-09-04 21:35                     ` Mark Wielaard
2014-09-05  9:38                     ` Mario Torre
2014-09-05  9:39                     ` Mario Torre
  -- strict thread matches above, loose matches on Subject: below --
2014-08-28 14:30 kgy
2014-08-28 15:30 ` Bodo Thiesen

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=54081F39.5020205@redhat.com \
    --to=aph@redhat.com \
    --cc=classpath@gnu.org \
    --cc=guille.rodriguez@gmail.com \
    --cc=java@gcc.gnu.org \
    --cc=per@bothner.com \
    /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).