Re: Another 646 patch and performance comparison with TOWER (solved)

[Martin Kahlert <martin dot kahlert at infineon dot com>]

Hi Tom,

On Tue, Apr 02, 2002 at 02:27:17PM -0700, Tom Tromey wrote:
> >>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
> 
> Tom> Why doesn't the `646' get turned into `ASCII' in getDecoder?
> 
> I tried the appended test.
> With this I don't see any attempts to load a converter library.
> So I think the 646 is being converted to `ASCII' internally.

In fact it is. Unfortunately ASCII is no valid conversion on Solaris either.
In this respect, 646 would have had the same effect.

I solved the problem, now: I use to build gcj with --disable-shared,
thus no shared conversion libraries are built and there are no useful
ones installed on the system either.

When i run your test program i get this:
Exception in thread "main" java.io.UnsupportedEncodingException: 646
(java.io.UnsupportedEncodingException: 646).

This is because Class.forName("gnu.gcj.convert.Input_ASCII") fails.
It cannot find the class in the executable because the linker left it out.
When i explicitly include a line
gnu.gcj.convert.Input_ASCII dummy = new gnu.gcj.convert.Input_ASCII();
then your program works o.k.

Building standalone java programs seems to be quite tricky.

Thanks a lot for your help,
Martin.

-- 
The early bird catches the worm. If you want something else for       
breakfast, get up later.