From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19347 invoked by alias); 25 Aug 2004 12:58:02 -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 18859 invoked by uid 48); 25 Aug 2004 12:57:50 -0000 Date: Wed, 25 Aug 2004 12:58:00 -0000 Message-ID: <20040825125750.18857.qmail@sourceware.org> From: "mckinlay 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/msg00322.txt.bz2 List-Id: ------- Additional Comments From mckinlay at redhat dot com 2004-08-25 12:57 ------- FWIW, I agree with Mark here. We shouldn't be encouraging application developers to make unwarranted assumptions about class files being available at runtime. There is no good reason why bytecode must be available at runtime. 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? If we decide to do this, there is the issue of how to _find_ the right libgcj.jar at runtime. The only reliable place is on a path relative to libgcj.so, so we'd have to first find the path to that. Perhaps we can do this using dlinfo(). That may be useful in other ways, such as automatically finding the right extdir. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15474