From: Paul Nasrat <pauln@truemesh.com>
To: Tom Tromey <tromey@redhat.com>
Cc: eclipse@sources.redhat.com
Subject: Re: naoko and building eclipse
Date: Tue, 06 Jan 2004 11:05:00 -0000 [thread overview]
Message-ID: <20040106110123.GB30106@ensim.rackshack.net> (raw)
In-Reply-To: <877k06yrgf.fsf@fleche.redhat.com>
On Mon, Jan 05, 2004 at 03:13:20PM -0700, Tom Tromey wrote:
> >>>>> "Paul" == Paul Nasrat <pauln@truemesh.com> writes:
>
> Paul> I'm trying to build eclipse on a rawhide system with naoko.
>
> BTW, which compiler are you using to do this?
Rawhide which is gcc 3.5-tree-ssa 20031211 snapshot.
> So if you are compiling our gcj-eclipse
> snapshot with a version of gcj other than our special hacked version,
> you'll have problems. The fix is pretty simple: rename instances of
> "solib" in eclipse to "gcjlib" (you can't do this blindly as this word
> is used in the CDT -- you have to look for places where we hacked
> eclipse).
Ok, looks as if I have to do this - hoping this fixes the core dumps I'm
getting from the ant run - if not gdb trace later.
> You can tell which version of gcj you've got by looking for the
> directory libjava/gnu/gcj/protocol/solib in the source tree. If it
> exists, you've got the older one.
I assume you mean libjava/gnu/java/net/protocol - in which case it's gcj lib
> This is a pain, I realize. Hopefully we'll have a new release out
> sometime.
Well there is a 23rd January devel freeze date for fc2 - I'd assume it'd be
pushed to rawhide by then.
Paul
next prev parent reply other threads:[~2004-01-06 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 23:31 Paul Nasrat
2004-01-05 20:17 ` Jeremy Handcock
2004-01-05 22:21 ` Tom Tromey
2004-01-06 11:05 ` Paul Nasrat [this message]
2004-01-07 17:58 ` Tom Tromey
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=20040106110123.GB30106@ensim.rackshack.net \
--to=pauln@truemesh.com \
--cc=eclipse@sources.redhat.com \
--cc=tromey@redhat.com \
/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).