Patch: update documentation for gcj-eclipse merge

Richard Guenther richard.guenther@gmail.com
Sat Jan 6 09:48:00 GMT 2007


On 05 Jan 2007 15:20:19 -0700, Tom Tromey <tromey@redhat.com> wrote:
> This patch updates the documentation to reflect how things will work
> after the gcj-eclipse merge is checked in.  I'd like this to be
> approved so that I can commit it after I commit the merge.
>
> With this merge, you need an 'ecj1' executable to get a fully
> functioning gcj.  We provide a jar download and some configury to make
> this simple to use; this patch adds a contrib/download_ecj script to
> help with this.
>
> This patch also documents the various prerequisites, new configure
> flags, etc.

I have a couple of questions here.  I presume ecj1 is needed for source to
bytecode translation and ecj1 is not necessary for bytecode to native
translation?  If you distribute ecj1 from sourceware.org you also need to
distribute source?  (This is a question also for distributors of binaries
for gcc - if they include java support and ecj1, do they need to distribute
the source to ecj1?)  Do you expect possible problems if we don't use
the 'latest' ecj1 with trunk but an earlier version?  What about the other
way around?  [I'm basically thinking on how to do a sensible setup
for packaging gcc in the future]

Thanks,
Richard.



More information about the Gcc-patches mailing list