Major 3.1 branch Java regressions
David S. Miller
davem@redhat.com
Fri May 17 00:05:00 GMT 2002
Ok, so I got to the bottom of this.
The build, based upon gcc_version, picks the name of libgcj-3.1.1.jar
for the class file.
The testsuite helper libjava/testsuite/lib/libjava.exp, hardcodes the
name to libgcj-3.1.jar
Which leads to a few questions.
First, do we really want the libgcj-${VER}.jar name to be changing
throughout bug fix releases of the 3.1 series?
Next, assuming we do want the name to change, do we hard code things
when the version string is updated or do we fix this right by making
configure somehow propagate the correct version string into the
libjava.exp used during the testsuite run?
Here is what I hacked into my tree to get the testsuite to work.
--- libjava/testsuite/lib/libjava.exp.~1~ Wed May 8 19:04:05 2002
+++ libjava/testsuite/lib/libjava.exp Thu May 16 23:56:45 2002
@@ -330,9 +330,9 @@
verbose "LD_LIBRARY_PATH = $env(LD_LIBRARY_PATH)"
# Set the CLASSPATH environment variable
- verbose "CLASSPATH is .:$srcdir/$subdir:$objdir:$objdir/../libgcj-3.1.jar"
+ verbose "CLASSPATH is .:$srcdir/$subdir:$objdir:$objdir/../libgcj-3.1.1.jar"
global env
- set env(CLASSPATH) ".:$srcdir/$subdir:$objdir:$objdir/../libgcj-3.1.jar"
+ set env(CLASSPATH) ".:$srcdir/$subdir:$objdir:$objdir/../libgcj-3.1.1.jar"
if {$mode == "link"} {
global wrapper_file wrap_compile_flags;
More information about the Gcc-bugs
mailing list