From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Bryce McKinlay <bmckinlay@gmail.com>
Cc: Andrew Haley <aph@redhat.com>,
Dave Korn <dave.korn.cygwin@googlemail.com>,
java@gcc.gnu.org, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [JAVA,libtool] Big libjava is biiiig.
Date: Wed, 06 May 2009 17:08:00 -0000 [thread overview]
Message-ID: <4A01C692.3030202@gmail.com> (raw)
In-Reply-To: <7230133d0905060959h5371a608nff03cce1e1e98f47@mail.gmail.com>
Bryce McKinlay wrote:
> If you're going to go to all this trouble, why not consider making libgcj
> compilable with the BC-ABI.
Well, in my case, because I have no idea what that involves or implies. I
was hoping to find a solution that I can get in during this current stage1 and
it not be the only thing I spend all of stage1 doing.
From your disclaimer, it sounds like this might be a slightly longer-term
project?
cheers,
DaveK
prev parent reply other threads:[~2009-05-06 17:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A01B55C.6060700@gmail.com>
2009-05-06 15:58 ` Dave Korn
2009-05-06 16:15 ` Ralf Wildenhues
2009-05-06 16:27 ` David Daney
2009-05-06 16:31 ` Richard Guenther
2009-05-06 16:40 ` Andrew Haley
2009-08-22 13:24 ` Dave Korn
2009-08-22 16:33 ` Andrew Haley
2009-08-22 18:55 ` Dave Korn
2009-08-28 18:04 ` Tom Tromey
2009-08-28 18:16 ` David Daney
2009-08-28 19:56 ` Dave Korn
2009-05-06 16:57 ` Dave Korn
2009-05-07 21:49 ` Ralf Wildenhues
2009-05-11 17:14 ` Dave Korn
2009-05-11 17:26 ` Andrew Haley
2009-05-11 18:03 ` Dave Korn
2009-05-13 12:38 ` Dave Korn
2009-05-13 16:18 ` Andrew Haley
2009-05-13 17:59 ` Dave Korn
2009-05-13 15:39 ` Dave Korn
2009-05-06 16:39 ` Andrew Haley
2009-05-06 16:45 ` Dave Korn
2009-05-06 17:12 ` Andrew Haley
2009-05-11 17:33 ` Dave Korn
2009-05-11 17:39 ` Andrew Haley
[not found] ` <7230133d0905060959h5371a608nff03cce1e1e98f47@mail.gmail.com>
2009-05-06 17:08 ` Dave Korn [this message]
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=4A01C692.3030202@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=aph@redhat.com \
--cc=bmckinlay@gmail.com \
--cc=gcc@gcc.gnu.org \
--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).