solaris2 libjava 500 failures

[Tom Tromey]

>>>>> "Kaveh" == Kaveh R Ghazi <ghazi@caip.rutgers.edu> writes:

Kaveh> (I've redirected this to a public forum.)  The vast majority (perhaps
Kaveh> all) of the solaris2 libjava testsuite failures look like this:

>> libjava/testsuite/libjava.compile/static_3.java:0: unknown encoding: `646'

Thanks.  I think forcing the encoding for the test suite is the right
thing to do.

Could you try the appended patch?  I haven't tried it yet, be warned.

2001-04-24  Tom Tromey  <tromey@redhat.com>

	* lib/libjava.exp (find_jvscan): Use UTF-8 encoding.
	(libjava_init): Likewise.

Tom

Index: lib/libjava.exp
===================================================================
RCS file: /cvs/gcc/gcc/libjava/testsuite/lib/libjava.exp,v
retrieving revision 1.22.4.2
diff -u -r1.22.4.2 libjava.exp
--- libjava.exp	2001/04/02 23:37:09	1.22.4.2
+++ libjava.exp	2001/04/24 17:28:38
@@ -49,7 +49,7 @@
 
 # Find `jv-scan'.
 proc find_jvscan {} {
-    return [libjava_find_program jv-scan]
+    return "[libjava_find_program jv-scan] --encoding=UTF-8"
 }
 
 # Find `gcjh'.
@@ -126,6 +126,9 @@
 	    }
 	}
     }
+
+    # Always set encoding used by gcj.
+    append GCJ_UNDER_TEST " --encoding=UTF-8"
 
     if [info exists env(LD_LIBRARY_PATH)] {
 	set original_ld_library_path $env(LD_LIBRARY_PATH)