From: Mike Hearn <mike@plan99.net>
To: Andrew Haley <aph@redhat.com>
Cc: GCC Java <java@gcc.gnu.org>
Subject: Re: Trouble building gcj 4.8.1
Date: Tue, 25 Jun 2013 13:53:00 -0000 [thread overview]
Message-ID: <CANEZrP2_wVtgjM8VTT8U1bvL0B44XE0U1X4XP32DuDL1J9nFeA@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP0WwGL40Vguonwb2CLvpvYmCaRTkO+wZqZ6uTGvtGxu0w@mail.gmail.com>
> Any idea why it's not building? Perhaps this is why the class file
> didn't get refreshed last time ....
Ah, it seems libjava/java/lang/String.java takes precedence over
libjava/classpath/java/lang/String.java
Looks like the libjava version is several years old. I tried a simple
replacement and it didn't build, probably because String depends on
various runtime internal things.
I feel like I am reaching the limits of what I can figure out by
myself. I'm trying to get the c'tors that include Charset so I might
try a surgical patch to the libjava/java/lang version, but there's
obviously several years of fixes and optimizations to the Classpath
version which would be nice to have. And I see that there are older
versions of other java.lang files in there too.
What's involved in syncing those core classes up to the latest
classpath versions?
next prev parent reply other threads:[~2013-06-25 13:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 13:21 Mike Hearn
2013-06-24 16:48 ` Mike Hearn
2013-06-24 17:04 ` Andrew Haley
2013-06-24 17:17 ` Mike Hearn
2013-06-24 17:26 ` Andrew Haley
2013-06-24 20:36 ` Matthias Klose
2013-06-25 13:39 ` Mike Hearn
2013-06-25 13:53 ` Mike Hearn [this message]
2013-06-25 14:07 ` Andrew Haley
2013-06-25 14:05 ` Andrew Haley
2013-06-25 14:05 ` Andrew Haley
2013-06-25 14:10 ` Mike Hearn
2013-06-25 14:12 ` Andrew Haley
2013-06-25 14:15 ` Mike Hearn
2013-06-25 14:21 ` Andrew Haley
2013-06-28 1:28 ` Andïï
2013-06-28 9:06 ` Andrew Haley
2013-07-02 14:53 ` Bryce McKinlay
[not found] ` <CANEZrP1tLxpu818cFGdgma+RVL32yRJJUOyb5m8QF=mhTZVueg@mail.gmail.com>
2013-07-03 13:43 ` Mike Hearn
2013-07-03 13:47 ` Andrew Haley
2013-07-03 21:31 ` Bryce McKinlay
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=CANEZrP2_wVtgjM8VTT8U1bvL0B44XE0U1X4XP32DuDL1J9nFeA@mail.gmail.com \
--to=mike@plan99.net \
--cc=aph@redhat.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).