Bug#197375: gcj dies when parsing java code with high ASCII values in it
Peter Hawkins writes:
> gcj doesn't appear to like high-valued characters in it's input
> stream. I see this while trying to build parts of kdebindings:
[...]
> KIconView.java:34: error: unrecognized character in input stream.
> you use this signal instead of the above mentioned. This way you don´t
>
> etc... lots of such errors removed.
>
> Since Sun's jdk apparently doesn't have a problem with this, could
> gcj be made to handle these characters too?
See the man page how to specify an encoding. dunno if Sun's jdk
defines a default encoding ...
Reply to: