From: Paul Nasrat <pauln@truemesh.com>
To: Tom Tromey <tromey@redhat.com>
Cc: eclipse@sources.redhat.com
Subject: Re: Fedora 2 & Eclipse
Date: Mon, 10 May 2004 22:31:00 -0000 [thread overview]
Message-ID: <20040510222106.GC24703@lichen.truemesh.com> (raw)
On Mon, May 10, 2004 at 04:12:47PM -0600, Tom Tromey wrote:
> Paul> I had Eclipse building with gcc-ssa and gcc34 mostly - ISTR the
> Paul> RHEL binaries were working for someone out of the box. The
> Paul> issues I hit are in the archives - solib/gcjlib, various link
> Paul> problems, etc.
>
> I got it building by basically s/solib/gcjlib/ in the eclipse patches.
Yup - I've posted my patch to list before and you cast an eye on it and it
seemed sane.
> You need a small patch to SWT to make it build with the newer Gtk.
Hmm, pretty sure got that far too.
> Once this stuff is done, it seems to crash if you do anything real
> with it; Anthony Green claimed better success but I'm not sure under
> what conditions.
IIRC I got splash and stuff working correctly then barfing on various runtime
linking issues. This could be me, and I'm not overly familiar with how
gcj/eclipse deals with hybrid .so/java stuff.
It strikes me that it should be at least something that should go into Fedora
Extras for FC2 eventually. I'll rebuild and log and try and poke people here -
I've had a lot of out of channel intrest from people via jpackage and other
forums for native eclipse so I would personally like to see it in fedora once
all the pain is gone.
Paul
next reply other threads:[~2004-05-10 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 22:31 Paul Nasrat [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 20:03 Ricardo Gorosito
2004-05-10 20:50 ` Paul Nasrat
2004-05-10 22:23 ` Tom Tromey
2004-05-10 23:16 ` Anthony Green
2004-12-22 18:46 ` Marc Boorshtein
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=20040510222106.GC24703@lichen.truemesh.com \
--to=pauln@truemesh.com \
--cc=eclipse@sources.redhat.com \
--cc=eclipse@sources.redhst.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).