From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2719 invoked by alias); 14 Dec 2004 20:13:13 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 2695 invoked by uid 48); 14 Dec 2004 20:13:12 -0000 Date: Tue, 14 Dec 2004 20:13:00 -0000 Message-ID: <20041214201312.2694.qmail@sourceware.org> From: "tromey at gcc dot gnu dot org" To: java-prs@gcc.gnu.org In-Reply-To: <20040321161516.14670.ovidr@users.sourceforge.net> References: <20040321161516.14670.ovidr@users.sourceforge.net> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/14670] [win32] gcj & high ascii: incorrectly translated / linux: fails to compile X-Bugzilla-Reason: CC X-SW-Source: 2004-q4/txt/msg00607.txt.bz2 List-Id: ------- Additional Comments From tromey at gcc dot gnu dot org 2004-12-14 20:13 ------- If by "high ascii" you mean byte with the high bit set, then you want to compile those with "--encoding ISO-8859-1" or the like. Whether this works on Windows, I don't know. It depends on whether iconv is available on that platform (or if you are using libiconv) What happens if you compile with "gcj -C" and then run the resulting bytecode using Sun's "java"? If this works, then the problem is not in the compiler at all but is in the runtime's choice of default character set. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14670