Re: icedtea6 fails to bootstrap on Fedora 17/18

[Jon VanAlten <jvanalte@redhat.com>]

----- Original Message -----
> From: "Matthias Klose" <doko@ubuntu.com>
> To: "Stefan Ring" <stefan@complang.tuwien.ac.at>
> Cc: "GCJ-patches" <java-patches@gcc.gnu.org>, "distro-pkg-dev" <distro-pkg-dev@openjdk.java.net>
> Sent: Monday, March 4, 2013 3:56:59 AM
> Subject: Re: icedtea6 fails to bootstrap on Fedora 17/18
> 
> 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.
> 
>   Matthias
> 
> 

Hi,

Fedora uses eclipse as upstream for ecj, not the source bundles at
that ftp site.

But, you've reminded me of something.  The ecj package does add an
alternative entry point (used by gcc/gcj).  This comes from the
sourceware.org:/cvs/rhug repository.  I had to patch the newest[1]
sources there a tiny bit due to ecj change:

diff -u -r org/eclipse/jdt/internal/compiler/batch/GCCMain.java org/eclipse/jdt/internal/compiler/batch/GCCMain.java
--- a/org/eclipse/jdt/internal/compiler/batch/GCCMain.java 2008-08-13 13:46:30.000000000 -0400
+++ b/org/eclipse/jdt/internal/compiler/batch/GCCMain.java 2012-04-26 13:36:21.268642702 -0400
@@ -29,6 +29,7 @@
 import org.eclipse.jdt.internal.compiler.env.AccessRule;
 import org.eclipse.jdt.internal.compiler.env.AccessRuleSet;
 import org.eclipse.jdt.internal.compiler.impl.CompilerOptions;
+import org.eclipse.jdt.internal.compiler.problem.ProblemSeverities;
 import org.eclipse.jdt.internal.compiler.util.Messages;
 import org.eclipse.jdt.internal.compiler.util.SuffixConstants;

@@ -463,7 +464,7 @@
 }

 if (inhibitAllWarnings)
- disableWarnings();
+ disableAll(ProblemSeverities.Warning);
 if (treatWarningsAsErrors)
 turnWarningsToErrors();
 
I really meant to follow up to upstream this, what is the right
way to do that?  (I am totally fine with someone committing this
on my behalf, by the way, but in general I would like to know
better if there is some mailing list where changes should go).

thanks,
jon

[1] Either that, or my (admittedly lacking) cvs-foo failed me.