From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26736 invoked by alias); 25 Aug 2004 16:17:23 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 26712 invoked by uid 48); 25 Aug 2004 16:17:22 -0000 Date: Wed, 25 Aug 2004 16:17:00 -0000 Message-ID: <20040825161722.26711.qmail@sourceware.org> From: "green at redhat dot com" To: java-prs@gcc.gnu.org In-Reply-To: <20040516104929.15474.green@redhat.com> References: <20040516104929.15474.green@redhat.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug java/15474] libgcj jar file should always be in classpath at runtime X-Bugzilla-Reason: CC X-SW-Source: 2004-q3/txt/msg00326.txt.bz2 List-Id: ------- 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