Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Jan 2013 19:30:38 -0500
From:      Jung-uk Kim <jkim@FreeBSD.org>
To:        Alex Dupre <ale@freebsd.org>
Cc:        ports@freebsd.org, java@freebsd.org, Gerald Pfeifer <gerald@pfeifer.com>, Jason Helfman <jgh@freebsd.org>
Subject:   Re: Breaking out gcc-ecj45 from lang/gcc{,46,47,48}
Message-ID:  <50F5F4AE.8080805@FreeBSD.org>
In-Reply-To: <50F51EFE.9050207@FreeBSD.org>
References:  <alpine.LNX.2.00.1301150126580.2028@tuna.site> <50F51EFE.9050207@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-01-15 04:18:54 -0500, Alex Dupre wrote:
> Gerald Pfeifer ha scritto:
>> to address ports/175072 I finally went ahead with an old plan of 
>> mine and broke the binary ecj.jar that is used to build the Java 
>> frontend for our GCC 4.6, 4.7 and 4.8 ports out into a separate 
>> port: lang/gcc-ecj45.
> 
> Why not using/updating the java/eclipse-ecj port?

No, we can't.  ecj-*.jar from ftp://sourceware.org/pub/java/ are
modified versions of ECJ:

http://gcc.gnu.org/ml/gcc-patches/2007-02/msg01497.html

In other words, you cannot use ordinary ECJ with GCJ.  In fact, there
was no ECJ 4.5 release, AFAIK.

Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBAgAGBQJQ9fSuAAoJECXpabHZMqHOI+wH/0/b1Kc6Og4ShbKViUckL9pK
tP1+GleHPvzAcN8F6QlH9bVQ6UFJZ+KqJCFISCQrvoxn2f2Xhg1oJy6FBtFXfZEy
RJyY/YmfrsqjPKZZGYQFcGJMFLTacDiLqIEJVqILcDcP1tpHN9UHSO2OrsBKN1Q9
n1SETkM1ss1xGJHeDaVD8tGPLrzPexdTfOj7S/eHqNRX/IB4PzsXB7xuxKC0/25Y
R/arn2hiSy0WAGc7Mvje/50q3lNx5JLlnFb2akG6Gj7b5FkT1aD0xA94jWpZAsec
d4pPRc01Hfg1oad9C41wdfBZ44nz1yCMFmjOFOCpTtEEPRi4ORB4qNwFz6mpNzw=
=JiiR
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50F5F4AE.8080805>