public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/42676] New: [4.5 regression] javah doesn't generate the header files as checked in in the archive Date: Sat, 09 Jan 2010 21:22:00 -0000 [thread overview] Message-ID: <bug-42676-5724@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/ml/java-patches/2009-q4/msg00069.html and followup: These look like regressions to me. This one is obviously wrong, for example: Index: javax/xml/xpath/XPathFunctionResolver.h =================================================================== --- javax/xml/xpath/XPathFunctionResolver.h (revision 155473) +++ javax/xml/xpath/XPathFunctionResolver.h (working copy) @@ -13,7 +13,7 @@ { namespace xml { - namespace namespace$ + namespace namespace { class QName; } @@ -30,7 +30,7 @@ { public: - virtual ::javax::xml::xpath::XPathFunction * resolveFunction(::javax::xml::namespace$::QName *, jint) = 0; + virtual ::javax::xml::xpath::XPathFunction * resolveFunction(::javax::xml::namespace::QName *, jint) = 0; static ::java::lang::Class class$; } __attribute__ ((java_interface)); -- Summary: [4.5 regression] javah doesn't generate the header files as checked in in the archive Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: debian-gcc at lists dot debian dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42676
next reply other threads:[~2010-01-09 21:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-09 21:22 debian-gcc at lists dot debian dot org [this message] 2010-01-10 22:03 ` [Bug libgcj/42676] " rguenth at gcc dot gnu dot org 2010-01-14 16:38 ` rguenth at gcc dot gnu dot org 2010-03-12 15:41 ` doko at ubuntu dot com 2010-03-13 14:28 ` doko at gcc dot gnu dot org 2010-03-13 14:45 ` debian-gcc at lists dot debian 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=bug-42676-5724@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).