From owner-freebsd-java@FreeBSD.ORG Tue Nov 25 05:49:07 2003 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D55C16A4CE for ; Tue, 25 Nov 2003 05:49:07 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF52043FBD for ; Tue, 25 Nov 2003 05:49:05 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.24; FreeBSD) id 1AOdYt-000DzM-5e; Tue, 25 Nov 2003 15:49:03 +0200 Date: Tue, 25 Nov 2003 15:49:03 +0200 From: Sheldon Hearn To: Peter Schuller Message-ID: <20031125134903.GS3597@starjuice.net> Mail-Followup-To: Peter Schuller , freebsd-java@freebsd.org References: <200311230237.16103.peter.schuller@infidyne.com> <20031124090207.GK18581@starjuice.net> <200311241623.25830.peter.schuller@infidyne.com> <200311242205.14636.peter.schuller@infidyne.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200311242205.14636.peter.schuller@infidyne.com> User-Agent: Mutt/1.5.4i cc: freebsd-java@freebsd.org Subject: Re: Compiling a native 1.4 with gcc 3.3 on FreeBSD 5-CURRENT X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2003 13:49:07 -0000 On (2003/11/24 22:05), Peter Schuller wrote: > > I'm using that version exactly, yes. However to be honest I don't remember > > whether I tried compiling before or after I cvsup:ed to -BETA recently. I > > will attempt a recompile and report back. > > Yes - still having the same problem. I've just tested with -CURRENT as at 2003-11-18, and the jdk-1.4.2p5 build completed without problems. I already had a native jdk14 with which to bootstrap. Perhaps you're using the linux-sun-jdk14 package for your build? If not, then it may be a difference in -CURRENT. I haven't upgraded to 5.2-BETA because that's horribly unstable on several fronts at the moment. Once it's stabilized, I'll try the build again and let you know if I encounter the same problem. Ciao, Sheldon.