From owner-freebsd-java@FreeBSD.ORG Sun Jun 10 03:14:47 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 D284416A400 for ; Sun, 10 Jun 2007 03:14:47 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (gerbercreations.com [71.39.140.16]) by mx1.freebsd.org (Postfix) with ESMTP id 9B77513C45D for ; Sun, 10 Jun 2007 03:14:47 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.1/8.13.3) with ESMTP id l5A3EjmS089226; Sat, 9 Jun 2007 20:14:45 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.1/8.13.3/Submit) id l5A3EiXx089225; Sat, 9 Jun 2007 20:14:44 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Sat, 9 Jun 2007 20:14:43 -0700 From: Greg Lewis To: Poul-Henning Kamp Message-ID: <20070610031443.GA89186@misty.eyesbeyond.com> References: <26165.1181329228@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26165.1181329228@critter.freebsd.dk> User-Agent: Mutt/1.4.2.2i 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 03:14:47 -0000 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. It really seems like the JDK build is tickling a problem in -CURRENT rather than anything else. #!/bin/sh TCOUNT=0 TMPFILE=`mktemp ./test-fs.XXXXXX` if [ $? -ne 0 ]; then echo "Test file cannot be created. Exiting." >&2 exit 1 fi sighandler() { rm -f ${TMPFILE} echo echo "Test interrupted after ${TCOUNT} runs." echo "No problem encountered." exit 0 } echo "Starting open(2)/unlink(2) test." echo -n "Press ^C to stop the test. " trap sighandler int while true; do TCOUNT=$(( ${TCOUNT} + 1 )) touch ${TMPFILE} if [ ! -f ${TMPFILE} ]; then echo "Test file does not exist. This is wrong!" >&2 exit 1 fi rm -f ${TMPFILE} if [ -f ${TMPFILE} ]; then echo "Test file should not exist. This is wrong!" >&2 exit 1 fi done -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org