From owner-freebsd-java@FreeBSD.ORG Sun Jun 10 07:07:55 2007 Return-Path: X-Original-To: java@FreeBSD.org Delivered-To: freebsd-java@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 60F2F16A400 for ; Sun, 10 Jun 2007 07:07:55 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 2344213C45A for ; Sun, 10 Jun 2007 07:07:55 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 87F2517380; Sun, 10 Jun 2007 07:07:53 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.1/8.14.1) with ESMTP id l5A77wVn002066; Sun, 10 Jun 2007 07:07:59 GMT (envelope-from phk@critter.freebsd.dk) To: Greg Lewis From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 09 Jun 2007 20:14:43 MST." <20070610031443.GA89186@misty.eyesbeyond.com> Date: Sun, 10 Jun 2007 07:07:58 +0000 Message-ID: <2057.1181459278@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: java@FreeBSD.org Subject: Re: jdk15 buildlog on -current X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2007 07:07:55 -0000 In message <20070610031443.GA89186@misty.eyesbeyond.com>, Greg Lewis writes: >On Fri, Jun 08, 2007 at 07:00:28PM +0000, Poul-Henning Kamp wrote: >> Still no jdk15 luck on -current: >> >> http://phk.freebsd.dk/misc/_.java_jdk15.gz > >So everyone who is seeing a failure is seeing one like this. That is, the >new compiler can't compile Java code which it should be able to. However, >all the failures are different and all the failures are indicative of a >file not being able to be read or the like. > >Jung-uk Kim suggested trying this script on the filesystem being used. >Maybe it will be able to demonstrate a reproducible a problem with file >access. I'm running the test-script now, but I seriously doubt it has any chance of finding problem, because buildworld would barf all over the place if basic file visibility was hosed. Isn't a more likely explanation that it is a SMP race ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.