public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "green at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/15474] libgcj jar file should always be in classpath at runtime
Date: Wed, 25 Aug 2004 16:17:00 -0000	[thread overview]
Message-ID: <20040825161722.26711.qmail@sourceware.org> (raw)
In-Reply-To: <20040516104929.15474.green@redhat.com>


------- Additional Comments From green at redhat dot com  2004-08-25 16:17 -------
(In reply to comment #4)
> There is no good reason why 
> bytecode must be available at runtime.

I suppose -- but if it's installed, what's the harm?

> Unfortunately, if there are important applications that rely for some reason
on being able to do this, 
> then we may not be able to avoid it. Anthony, what prompted this PR exactly?

The testsuite for a bytecode munging library required it.  I believe it was a
dependency of Groovy.

> If we decide to do this, there is the issue of how to _find_ the right
libgcj.jar at runtime. 

What's wrong with the sun.boot.class.path property we're already depending on in
Ant?

> That may be useful in other ways, such as automatically finding the right extdir.

We have the java.ext.dirs property.

AG


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15474


  parent reply	other threads:[~2004-08-25 16:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 10:49 [Bug java/15474] New: " green at redhat dot com
2004-05-16 11:29 ` [Bug java/15474] " pinskia at gcc dot gnu dot org
2004-05-16 12:06 ` mark at gcc dot gnu dot org
2004-08-25  9:20 ` pinskia at gcc dot gnu dot org
2004-08-25 12:58 ` mckinlay at redhat dot com
2004-08-25 16:17 ` green at redhat dot com [this message]
2004-08-25 17:47 ` mckinlay at redhat dot com
2004-08-25 17:52 ` mckinlay at redhat dot com
2004-08-25 18:01 ` green at redhat dot com
     [not found] <bug-15474-83@http.gcc.gnu.org/bugzilla/>
2006-07-14 18:35 ` green at redhat dot com
2007-04-13 19:44 ` mark 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=20040825161722.26711.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: 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).