This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] documenting the need for ecj.jar
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Tom Tromey <tromey at redhat dot com>, Bruno Haible <bruno at clisp dot org>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sun, 4 Mar 2007 16:40:12 +0100 (CET)
- Subject: Re: [PATCH] documenting the need for ecj.jar
- References: <200702071626.55900.bruno@clisp.org> <200702071913.38913.bruno@clisp.org> <m3abzpzqel.fsf@localhost.localdomain> <200702171443.43493.bruno@clisp.org> <m3d53rtu08.fsf@localhost.localdomain>
On Fri, 2 Mar 2007, Tom Tromey wrote:
>> 2007-02-17 Bruno Haible <bruno@clisp.org>
>> * doc/install.texi (Prerequisites): Mention ecj.jar and how to
>> download it.
> It seems good to me, but someone else will have to approve it.
I believe any of our Java maintainers would be a good candidate, Tom. ;-)
If you'd like an ACK from the doc side, I'll be happy to provide one
thusly. There is only one detail which confuses me a bit:
Necessary to build the Java front-end of @command{gcj}.
Isn't @command{gcj} our Java front end? Did you mean GCJ here, Bruno,
or is this equivalent to "the @command{gcj} Java front end"? Mind, it's
entirely possible I am just confused.
("front end" instead of "front-end" according to codingconventions.html.
I always forget this myself, just looked it up. ;-)
Gerald