From: Tom Tromey <tromey@redhat.com>
To: eclipse@sources.redhat.com
Subject: Note on using cvs gcc
Date: Wed, 08 Oct 2003 17:45:00 -0000 [thread overview]
Message-ID: <873ce3fx65.fsf@fleche.redhat.com> (raw)
Last week I tried using the current gcc.gnu.org cvs trunk gcc to build
eclipse. This went pretty well.
I had to s/solib/gcjlib/ in all the sources, since our special URL
handler was renamed before putting it in the public tree.
Also, one of the .jar files wouldn't compile, because the net gcj
still has a bug in its verifier -- in the "gcc-ssa" RPM, we just
disable the verifier to work around this. An uncompiled .jar isn't a
big problem, though, since everything should still work interpreted.
The resulting eclipse starts up fine. I didn't do any serious testing
of it, but I wouldn't anticipate major problems. Usually serious bugs
show up during the startup process.
Tom
reply other threads:[~2003-10-08 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=873ce3fx65.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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).