public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerrit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/13708] static java program crashes at startup, UTF-8 environment
Date: Sun, 29 May 2005 02:25:00 -0000 [thread overview]
Message-ID: <20050529020912.24243.qmail@sourceware.org> (raw)
In-Reply-To: <20040116155120.13708.mec.gnu@mindspring.com>
------- Additional Comments From gerrit at gcc dot gnu dot org 2005-05-29 02:09 -------
(In reply to comment #29)
> *** Bug 21793 has been marked as a duplicate of this bug. ***
The same example works with the MinGW version of gcj-3.4.2?
And it works when I set the encoding to ISO-8859-1:
$ /usr/bin/gcj -Dfile.encoding=ISO-8859-1 --main=hello_j hello_j.java -o hello_j
$ ./hello_j
Just another Java hacker,
How do I set the default encoding to ISO-8859-1 when building gcj?
And when will GCC be switched to use >= libtool-1.5.10 and newer automake &
autoconf versions? Shared libraries are not supported by the antiquated libtool
and friends used by GCC.
Gerrit
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13708
next prev parent reply other threads:[~2005-05-29 2:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 15:51 [Bug libgcj/13708] New: " mec dot gnu at mindspring dot com
2004-01-16 15:58 ` [Bug libgcj/13708] " mec dot gnu at mindspring dot com
2004-01-16 16:00 ` mec dot gnu at mindspring dot com
2004-01-16 16:46 ` pinskia at gcc dot gnu dot org
2004-01-16 17:58 ` mec dot gnu at mindspring dot com
2004-01-16 18:17 ` pinskia at gcc dot gnu dot org
2004-01-16 19:27 ` tromey at gcc dot gnu dot org
2004-01-16 19:38 ` pinskia at gcc dot gnu dot org
2004-01-16 19:53 ` mec dot gnu at mindspring dot com
2004-01-16 22:01 ` mec dot gnu at mindspring dot com
2004-01-17 0:33 ` dhazeghi at yahoo dot com
2004-01-17 10:11 ` mec dot gnu at mindspring dot com
2004-01-18 18:06 ` [Bug libgcj/13708] [3.4/3.5 regression] " pinskia at gcc dot gnu dot org
2004-01-18 20:01 ` mec dot gnu at mindspring dot com
2004-01-18 20:17 ` pinskia at gcc dot gnu dot org
2004-01-19 0:30 ` mec dot gnu at mindspring dot com
2004-01-25 3:19 ` [Bug libgcj/13708] [3.4/3.5 regression] static " pinskia at gcc dot gnu dot org
2004-02-29 23:47 ` mmitchel at gcc dot gnu dot org
2004-03-01 2:02 ` pinskia at gcc dot gnu dot org
2004-03-18 17:24 ` pinskia at gcc dot gnu dot org
2004-03-19 5:05 ` pinskia at gcc dot gnu dot org
2004-06-09 19:28 ` mmitchel at gcc dot gnu dot org
2004-06-09 19:43 ` tromey at gcc dot gnu dot org
2004-06-09 21:37 ` mec dot gnu at mindspring dot com
2004-06-10 7:43 ` oyvind dot harboe at zylin dot com
2004-07-09 21:32 ` [Bug libgcj/13708] " pinskia at gcc dot gnu dot org
2004-07-10 3:19 ` mec dot gnu at mindspring dot com
2004-08-20 7:35 ` pinskia at gcc dot gnu dot org
2004-09-07 18:02 ` dtiller at captechventures dot com
2004-11-13 5:35 ` pinskia at gcc dot gnu dot org
2005-05-28 0:33 ` pinskia at gcc dot gnu dot org
2005-05-29 2:25 ` gerrit at gcc dot gnu dot org [this message]
2005-06-19 23:04 ` pinskia at gcc dot gnu dot org
2005-06-19 23:05 ` pinskia at gcc dot gnu dot org
2005-07-15 21:50 ` pinskia at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050529020912.24243.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).