From: Anthony Green <green@redhat.com>
To: apbianco@redhat.com
Cc: rhug-rhats@sources.redhat.com
Subject: gcj -C bug
Date: Sat, 06 Oct 2001 17:34:00 -0000 [thread overview]
Message-ID: <200110070034.RAA17859@fencer.cygnus.com> (raw)
Hey Alex -
I had to work around once bug in "gcj -C" with the following hack...
upstream/src/org/mozilla/javascript/regexp/NativeRegExp.class: upstream/src/org/mozilla/javascript/regexp/NativeRegExp.java
unzip -p $(srcdir)/upstream/js.jar org/mozilla/javascript/regexp/NativeRegExp.class > $@
gcj -C hangs on compiling NativeRegExp.java otherwise.
Thanks!
AG
next reply other threads:[~2001-10-06 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 17:34 Anthony Green [this message]
[not found] <200110070034.RAA17856@fencer.cygnus.com>
2001-10-08 13:40 ` Alexandre Petit-Bianco
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=200110070034.RAA17859@fencer.cygnus.com \
--to=green@redhat.com \
--cc=apbianco@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
/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).