From owner-freebsd-java@FreeBSD.ORG Fri Dec 17 15:35:32 2004 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 031AC16A4CE for ; Fri, 17 Dec 2004 15:35:32 +0000 (GMT) Received: from quack.kfu.com (quack.kfu.com [64.168.71.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2A2B43D1D for ; Fri, 17 Dec 2004 15:35:31 +0000 (GMT) (envelope-from nsayer@kfu.com) Received: from [IPv6:2002:40a8:47d1:1:206:25ff:fe3d:aa11] (minerva.kfu.com [IPv6:2002:40a8:47d1:1:206:25ff:fe3d:aa11]) (authenticated bits=0) by quack.kfu.com (8.12.10/8.12.10) with ESMTP id iBHFZUCg055824 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Fri, 17 Dec 2004 07:35:31 -0800 (PST) (envelope-from nsayer@kfu.com) X-Message-Flag: Why aren't you using a Macintosh yet? Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4885A5C3-5041-11D9-A430-000A959D8ECE@kfu.com> Content-Transfer-Encoding: 7bit From: Nick Sayer Date: Fri, 17 Dec 2004 07:35:30 -0800 To: freebsd-java@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: Still cannot build native JDK 1.4 with FreeBSD 5.3 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: Fri, 17 Dec 2004 15:35:32 -0000 >Have you tried to verify that your linux linux-sun-jdk-1.4.2.0x is >working indeed? (try some apps, especially javac) Yup. It works just fine. I use it every day for all sorts of things, given that I can't use the last native build any more because of file descriptor leaks (the last successful build I did was with 5.2.1). >Have you tried make clean and start all over the build? Dozens of times. It fails the exact same way every time, no matter what I try to change. >Also a check for mem,disk,CPU overheating, would be very good. I really, really, really doubt it. 1. It fails exactly the same way every time. 2. Nothing else I do on this machine, which includes some fairly intensive things (building all of KDE, for example) has failed. 3. The machine is a, more or less, out-of-the-box IBM desktop machine without bizarro 3rd party RAM or anything like that.