From: "J. Scott Amort" <jsamort@shaw.ca>
To: eclipse@sources.redhat.com
Subject: Re: eclipse-2.1.1-4
Date: Sun, 29 Feb 2004 01:56:00 -0000 [thread overview]
Message-ID: <1078019783.6857.3.camel@enlightenment.baobobmusic.ca> (raw)
In-Reply-To: <87znb2kea3.fsf@fleche.redhat.com>
On Sat, 2004-02-28 at 14:52, Tom Tromey wrote:
> Hmm, was the rawhide at built with gcj-ssa? I was under the
> impression it was built with gcj34. This matters due to how
> compilations are done when building eclipse -- first the eclipse java
> compiler is compiled to a .so, then this is loaded into ant. If ant
> and the .so aren't built with the same compiler, problems will occur.
Thanks for the response, I actually went back to the older versions of
ant, gcj-ssa, et. al. and it worked. Seems like that was the problem.
> We'll be putting out a newer build for FC in the hopefully
> not-too-distant future.
Great, I'm looking forward to it.
Scott
prev parent reply other threads:[~2004-02-29 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 22:39 eclipse-2.1.1-4 J. Scott Amort
2004-02-28 23:03 ` eclipse-2.1.1-4 Tom Tromey
2004-02-29 1:56 ` J. Scott Amort [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=1078019783.6857.3.camel@enlightenment.baobobmusic.ca \
--to=jsamort@shaw.ca \
--cc=eclipse@sources.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).