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


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-08-25 09:20 -------
Actually I think it should the way Anthony wants as I think like any good java implemenation we should 
provide the class files also.  Even though we provide most (if not all) of our java class files as already 
compiled code is just an implemenation detail rather than making it the main factor here.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
   Last reconfirmed|2004-05-16 11:29:27         |2004-08-25 09:20:09
               date|                            |


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


  parent reply	other threads:[~2004-08-25  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17  0:49 [Bug java/15474] New: " green at redhat dot com
2004-05-17  0:56 ` [Bug java/15474] " pinskia at gcc dot gnu dot org
2004-05-17  1:01 ` mark at gcc dot gnu dot org
2004-08-25  9:20 ` pinskia at gcc dot gnu dot org [this message]
2004-08-25 12:58 ` mckinlay at redhat dot com
2004-08-25 16:17 ` green at redhat dot com
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:45 ` 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=20040825092014.15054.qmail@sourceware.org \
    --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: 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).