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/35950] New: jar produces files ecj won't handle
Date: Tue, 15 Apr 2008 21:42:00 -0000 [thread overview]
Message-ID: <bug-35950-9966@http.gcc.gnu.org/bugzilla/> (raw)
If the copy of gjar from GCJ 4.3.0 is used to build GNU Classpath with the
examples turned on (--enable-examples) it will fail with an error relating to
gnu.classpath.tools.tnameserv.Main. This class is inside tools.zip, which is
created earlier in the build by gjar.
ecj seems to refuse to pick up the class from this zip file. Uncompressing the
zip file, using gcj's tools.zip or creating the zip with fastjar or current
gjar from GNU Classpath cause the examples to be built correctly.
Seems like a lingering gjar bug that may need to be backported. ecj is being
run using gcj.
--
Summary: jar produces files ecj won't handle
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcj
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: gnu_andrew at member dot fsf dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35950
next reply other threads:[~2008-04-15 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 21:42 gnu_andrew at member dot fsf dot org [this message]
2008-04-16 22:21 ` [Bug libgcj/35950] " gnu_andrew at member dot fsf dot org
2008-04-16 22:30 ` tromey at gcc dot gnu dot org
2008-04-16 22:32 ` tromey at gcc dot gnu dot org
2008-04-16 23:34 ` gnu_andrew at member dot fsf dot org
2008-04-17 17:16 ` tromey at gcc dot gnu dot org
2008-04-17 17:16 ` tromey at gcc dot gnu dot org
2008-04-17 17:18 ` tromey at gcc dot gnu 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-35950-9966@http.gcc.gnu.org/bugzilla/ \
--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).