From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: unable to regenerate the pregenerated libjava header files on the trunk
Date: Sun, 28 Feb 2010 10:24:00 -0000 [thread overview]
Message-ID: <4B8A4453.4030606@redhat.com> (raw)
In-Reply-To: <4B894E9A.4000903@ubuntu.com>
On 02/27/2010 04:55 PM, Matthias Klose wrote:
> this is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42676, now
> downgraded to P4. At least for Debian, this would mean not shipping gcj
> anymore in the main section of the archive (cannot be built from
> source). Is this a restriction for the upstream release as well? Can
> this be reproduced by others?
I think you're bootstrapping with an obsolete version of gjavah.
To see if I'm right, generate the header file for
javax/xml/xpath/XPathFunctionResolver. Like this:
$ gjavah -cni -force -classpath <path>/x86_64-unknown-linux-gnu/libjava/libgcj-4.5.0.jar javax/xml/xpath/XPathFunctionResolver
With the new version of gjavah, you'll get
namespace xml
{
namespace namespace$
With the old version you'll get
namespace xml
{
namespace namespace
Andrew.
next prev parent reply other threads:[~2010-02-28 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 16:56 Matthias Klose
2010-02-28 10:24 ` Andrew Haley [this message]
2010-03-13 14:24 ` Matthias Klose
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=4B8A4453.4030606@redhat.com \
--to=aph@redhat.com \
--cc=java@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).