public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "gnu_andrew at member dot fsf dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/32028] Make fails at gjdoc - gnu.classpath.tools.gjdoc.ParseException: unmatched input in line 1: @Retention(SOURCE) @Target(METHOD)
Date: Fri, 20 Jun 2008 14:34:00 -0000	[thread overview]
Message-ID: <20080620143422.15759.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32028-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from gnu_andrew at member dot fsf dot org  2008-06-20 14:34 -------
Wha is this bug waiting on? The only clear bug I can see here is that the
Classpath build system (not gcc's; Classpath ./configure is invoked by the
surrounding gcj build) should be checking the version of gjdoc.

GJDoc 0.7.8 and 0.7.9 should work with the version of Classpath in GCC 4.3.
There is an issue with this missing the contents of external/jsr166 which is
fixed in Classpath.  Generating docs for these additional classes requires
0.7.9.

Classpath 0.98 (and thus, probably GCC 4.4) will include GJDoc.

The warnings are expected.  GJDoc's parser can run through 1.5 code.  It can't
correctly parse it all yet, though it may be worth turning off some of these
errors in the meantime.

Patches welcome :)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32028


  parent reply	other threads:[~2008-06-20 14:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22  2:28 [Bug libgcj/32028] New: " rob1weld at aol dot com
2007-05-24 16:19 ` [Bug libgcj/32028] " tromey at gcc dot gnu dot org
2007-05-24 18:48 ` rob1weld at aol dot com
2007-05-25  8:55 ` rob1weld at aol dot com
2007-05-25 19:12 ` rob1weld at aol dot com
2008-06-20 14:34 ` gnu_andrew at member dot fsf dot org [this message]
2008-08-04 13:44 ` rob1weld at aol dot com
2008-08-04 18:31 ` tromey at gcc dot gnu dot org
2008-08-04 18:33 ` tromey at gcc dot gnu dot org
2008-08-16 23:14 ` [Bug classpath/32028] " gnu_andrew at member dot fsf dot org
2008-08-21  1:01 ` gnu_andrew at member dot fsf dot org
2008-08-21  1:02 ` gnu_andrew at member dot fsf dot org
2008-08-24 23:28 ` gnu_andrew at member dot fsf dot org
2008-08-28 15:40 ` gnu_andrew at member dot fsf dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080620143422.15759.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).