[Bug java/15474] libgcj jar file should always be in classpath at runtime
mckinlay at redhat dot com
gcc-bugzilla@gcc.gnu.org
Wed Aug 25 12:58:00 GMT 2004
------- 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
More information about the Gcc-bugs
mailing list