From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11771 invoked by alias); 8 Oct 2003 17:45:51 -0000 Mailing-List: contact eclipse-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: eclipse-owner@sources.redhat.com Received: (qmail 11758 invoked from network); 8 Oct 2003 17:45:50 -0000 To: eclipse@sources.redhat.com Subject: Note on using cvs gcc From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom X-Zippy: Look!! Karl Malden! Date: Wed, 08 Oct 2003 17:45:00 -0000 Message-ID: <873ce3fx65.fsf@fleche.redhat.com> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-q4/txt/msg00001.txt.bz2 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