This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Andrew Hughes <gnu dot andrew at redhat dot com>
- Cc: Andrew Haley <aph at redhat dot com>,Matthias Klose <doko at ubuntu dot com>,Tom Tromey <tom at tromey dot com>,Jeff Law <law at redhat dot com>,Uros Bizjak <ubizjak at gmail dot com>,gcc-patches at gcc dot gnu dot org,java-patches at gcc dot gnu dot org
- Date: Thu, 20 Aug 2015 20:05:33 +0200
- Subject: Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
- Authentication-results: sourceware.org; auth=none
- References: <CAFULd4YCSbA_2V8jNF1QtcM8b4EF8mJzTD7PyU9ETZ-uSyemsw at mail dot gmail dot com> <55D58ED0 dot 1020402 at ubuntu dot com> <55D5909B dot 3080207 at redhat dot com> <401143105 dot 13318272 dot 1440082676204 dot JavaMail dot zimbra at redhat dot com> <55D5F1C8 dot 7060003 at redhat dot com> <753848288 dot 13346990 dot 1440085975680 dot JavaMail dot zimbra at redhat dot com> <6D3AF2B0-A114-4871-B606-E17C19D0D8B4 at gmail dot com> <100448475 dot 13392788 dot 1440089992425 dot JavaMail dot zimbra at redhat dot com> <118141631 dot 13413443 dot 1440092137784 dot JavaMail dot zimbra at redhat dot com>
On August 20, 2015 7:35:37 PM GMT+02:00, Andrew Hughes <gnu.andrew@redhat.com> wrote:
>----- Original Message -----
>> snip...
>> >
>> > Having classpath (with binary files!) In the GCC SVN (or future
>git)
>> > repository is a significant burden, not to mention the size of the
>> > distributed source tarball.
>> >
>> > If we can get rid of that that would be a great step in reducing
>the
>> > burden.
>> >
>> > Iff we can even without classpath build enough of java to be useful
>(do you
>> > really need gcj or only gij for bootstrapping openjdk? After all
>ecj is
>> > just
>> > a drop-in to gcc as well).
>>
>> All the Java compilers are written in Java (ecj & javac). So to run
>them, you
>> need a JVM and its class library.
>>
>> It's those binary files which allow gcj to bootstrap the stack. If
>OpenJDK
>> had a minimal binary class library, it would be able to bootstrap
>itself.
>>
>> But, as things stand, you need enough of the JDK to run a Java
>compiler
>> and build the OpenJDK class libraries. GCJ currently fulfils that
>need
>> where there isn't already an OpenJDK installation available.
>> --
>
>Actually, this makes me think...
>
>IcedTea already depends on CACAO and JamVM for alternate builds of
>OpenJDK. We could instead include the bytecode binaries for GNU
>Classpath
>in IcedTea, bootstrap JamVM and use that to bootstrap OpenJDK. That
>would remove our dependency on gcj and make IcedTea largely
>self-sufficient.
>It would also mean we could drop a bunch of conditional code which
>depends
>on what the system bootstrap JDK is, because it would always be the
>in-tree
>solution.
>
>We'd still need more than six months to make this transition though,
>as such a change really needs time for testing.
OK, so how about deprecating Java for GCC 6 by removing it from the default languages and removing it for GCC 7 or before we switch to git (whatever happens earlier?)
Richard.