From: Andrew Hughes <gnu.andrew@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: distro-pkg-dev <distro-pkg-dev@openjdk.java.net>,
GCJ-patches <java-patches@gcc.gnu.org>,
Stefan Ring <stefan@complang.tuwien.ac.at>
Subject: Re: icedtea6 fails to bootstrap on Fedora 17/18
Date: Wed, 06 Mar 2013 15:04:00 -0000 [thread overview]
Message-ID: <247591252.13844085.1362582262417.JavaMail.root@redhat.com> (raw)
In-Reply-To: <513461DB.4000603@ubuntu.com>
----- Original Message -----
> Am 03.03.2013 17:14, schrieb Stefan Ring:
> > ecj is much more recent on Fedora apparently:
> >
> > Ubuntu quantal $ ecj -version:
> > Eclipse Java Compiler 0.972_R35x, 3.5.1 release, Copyright IBM Corp
> > 2000, 2009. All rights reserved.
> > Fedora 17 $ ecj -version
> > Eclipse Compiler for Java(TM) v20120814-155456, 3.8.2, Copyright
> > IBM
> > Corp 2000, 2012. All rights reserved.
>
> Debian and Ubuntu use the same sources to provide both ecj and ecj1.
> ftp://sourceware.org/pub/java/ still has 3.5 as the latest version
> available.
> If Fedora ships an updated ecj1, then it would be nice to see this
> "upstream" as
> well.
I'll second that. I'm surprised 3.8.2 works with the current gcj actually,
as when I tried it, it complained about missing javax.lang.model code which
is now in GNU Classpath but not yet in gcj.
Do you know the process for updating the copy used by gcj?
>
> Matthias
>
>
--
Andrew :)
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
prev parent reply other threads:[~2013-03-06 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAxjCEzKrepM6yfBy6p4mmtg-C+6mLoKJeUT5RVHgy3=iLLdsw@mail.gmail.com>
2013-03-04 8:57 ` Matthias Klose
2013-03-05 20:51 ` Jon VanAlten
2013-03-06 15:04 ` Andrew Hughes [this message]
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=247591252.13844085.1362582262417.JavaMail.root@redhat.com \
--to=gnu.andrew@redhat.com \
--cc=distro-pkg-dev@openjdk.java.net \
--cc=doko@ubuntu.com \
--cc=java-patches@gcc.gnu.org \
--cc=stefan@complang.tuwien.ac.at \
/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).