Date: Sun, 10 Jun 2007 07:43:01 -0700 From: Greg Lewis <glewis@eyesbeyond.com> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: java@freebsd.org Subject: Re: jdk15 buildlog on -current Message-ID: <20070610144301.GA94235@misty.eyesbeyond.com> In-Reply-To: <2057.1181459278@critter.freebsd.dk> References: <20070610031443.GA89186@misty.eyesbeyond.com> <2057.1181459278@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 10, 2007 at 07:07:58AM +0000, Poul-Henning Kamp wrote: > 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 ? Quite possibly. You've got much more experience on -current than I have :). Does setting libkse to be the default threading library with libmap.conf make any difference (libthr is the default on -current at the moment IIRC)? -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070610144301.GA94235>