public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu 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: Thu, 24 May 2007 16:19:00 -0000 [thread overview] Message-ID: <20070524161859.7303.qmail@sourceware.org> (raw) In-Reply-To: <bug-32028-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from tromey at gcc dot gnu dot org 2007-05-24 17:18 ------- I think gjdoc only recently got support for generics and annotations. So an older gjdoc is expected to fail. I haven't been keeping track of gjdoc version numbers but I expect if you install a newer version this will work. Can you try that? -- tromey at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32028
next prev parent reply other threads:[~2007-05-24 16:19 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 ` tromey at gcc dot gnu dot org [this message] 2007-05-24 18:48 ` [Bug libgcj/32028] " 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 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=20070524161859.7303.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: linkBe 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).