public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oyvind dot harboe at zylin dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/12908] gnu.gcj.convert.Input_UTF8 not found
Date: Wed, 05 Nov 2003 17:17:00 -0000 [thread overview]
Message-ID: <20031105171747.10010.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031105094302.12908.oyvind.harboe@zylin.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12908
------- Additional Comments From oyvind dot harboe at zylin dot com 2003-11-05 17:17 -------
>The original problem is being reported on Windows, where gcj only
>does static linking. Input_UTF8 is being loaded via Class.forName()
>in this case, so you're in trouble if you have a static image without
>that class.
>
>The fix is to stick this in your code somewhere:
>
> private static Class c1 = gnu.gcj.convert.Input_UTF8.class;
>
>This will force Input_UTF8 into your static image.
This is scary.
How can I enumerate the hidden libgcj classes I need?
Øyvind
next prev parent reply other threads:[~2003-11-05 17:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 9:43 [Bug java/12908] New: " oyvind dot harboe at zylin dot com
2003-11-05 9:43 ` [Bug java/12908] " oyvind dot harboe at zylin dot com
2003-11-05 9:44 ` oyvind dot harboe at zylin dot com
2003-11-05 14:28 ` [Bug libgcj/12908] " pinskia at gcc dot gnu dot org
2003-11-05 15:03 ` pinskia at gcc dot gnu dot org
2003-11-05 15:24 ` green at redhat dot com
2003-11-05 17:17 ` oyvind dot harboe at zylin dot com [this message]
2003-11-05 19:42 ` oyvind dot harboe at zylin dot com
2003-11-05 22:38 ` [Bug libgcj/12908] gnu.gcj.convert.Input_UTF8 not found when compiling from bytecode green at redhat dot com
2003-11-06 8:43 ` oyvind dot harboe at zylin dot com
2003-11-08 19:38 ` tromey at gcc dot gnu dot org
2003-11-11 17:42 ` pinskia at gcc dot gnu dot org
2003-11-26 15:46 ` pinskia at gcc dot gnu dot org
2003-11-26 15:46 ` pinskia at gcc dot gnu dot org
2004-03-18 16:56 ` pinskia at gcc dot gnu dot org
2004-03-19 5:04 ` 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=20031105171747.10010.qmail@sources.redhat.com \
--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).