From: Adam Megacz <gcj@lists.megacz.com>
To: java@gcc.gnu.org
Subject: Re: MissingResourceException with Date under mingw port
Date: Wed, 10 Apr 2002 10:42:00 -0000 [thread overview]
Message-ID: <86r8lnzcpo.fsf@megacz.com> (raw)
In-Reply-To: Adam King's message of "Wed, 10 Apr 2002 13:12:02 -0400"
Adam King <aking@dreammechanics.com> writes:
> Exception in thread "main" java.util.MissingResourceException:
> Bundle gnu.java.locale.Calendar not found
Yeah, the linkage between java.util.Date and gnu.java.locale.Calendar
is weak -- Date only references Calendar via reflection. GNU ld
doesn't understand this sort of linkage, so it doesn't include
gnu.java.locale.Calendar when creating a static binary.
Here's the standard prelude I throw into all my gcj programs to force
the linker to include all the required classes:
// static references to these classes ensure that the linker will include them
private static Class c1 = gnu.java.locale.Calendar.class;
private static Class c2 = java.util.GregorianCalendar.class;
private static Class c3 = gnu.gcj.convert.Input_ASCII.class;
private static Class c4 = gnu.gcj.convert.Input_UTF8.class;
private static Class c5 = gnu.gcj.convert.Input_8859_1.class;
private static Class c6 = gnu.java.locale.LocaleInformation.class;
private static Class c7 = gnu.gcj.convert.Output_ASCII.class;
To the other GCJ people: are there any disadvantages to putting
private static foo.class references in the java.* classes so that
static links work properly without this hack?
> It runs fine when compiled with the linux target.
Probably because you're dynamically linking against libgcj.so, which
includes the whole Java library. If you compile with --static you
should see the same problem on Linux.
- a
--
The web is dead; long live the Internet.
http://www.xwt.org/
next prev parent reply other threads:[~2002-04-10 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 10:31 Adam King
2002-04-10 10:42 ` Adam Megacz [this message]
2002-04-10 10:49 ` Tom Tromey
2002-04-10 12:25 ` Eric Blake
2002-04-10 12:55 ` Adam Megacz
2002-04-10 15:56 ` Eric Blake
2002-04-10 16:11 ` Tom Tromey
2002-04-10 16:35 ` Tom Tromey
2002-04-10 18:21 ` Per Bothner
2002-04-10 11:11 ` Mark Wielaard
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=86r8lnzcpo.fsf@megacz.com \
--to=gcj@lists.megacz.com \
--cc=java@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).