From owner-freebsd-ports@FreeBSD.ORG Wed Feb 19 19:04:37 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8BE45803 for ; Wed, 19 Feb 2014 19:04:37 +0000 (UTC) Received: from cargobay.net (cargobay.net [162.220.58.155]) by mx1.freebsd.org (Postfix) with ESMTP id 666021840 for ; Wed, 19 Feb 2014 19:04:37 +0000 (UTC) Received: from [172.17.100.84] (rrcs-97-76-30-202.se.biz.rr.com [97.76.30.202]) by cargobay.net (Postfix) with ESMTPSA id 388F74250; Wed, 19 Feb 2014 19:01:28 +0000 (UTC) Message-ID: <5305003C.1080908@ccsys.com> Date: Wed, 19 Feb 2014 14:04:28 -0500 From: "Chad J. Milios" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: David Thiel Subject: Re: dns/djbdns [do-package] Error code 1 References: <5304F8A5.9040209@ccsys.com> <20140219185040.GW8859@redundancy.redundancy.org> In-Reply-To: <20140219185040.GW8859@redundancy.redundancy.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 19:04:37 -0000 Oh yeah, I probably should have mentioned I'm on 9.2-RELEASE/amd64 with all ZFS file systems (except tmpfs /tmp). I'll give that a shot and report back, usually woulda been my first stab at it but i too had a feeling that just didnt seem to be applicable in this case. I'll have to try it out tonight, that box is close to pegged most of the day, I was doing the experimenting at 3:30 am this morning. On 2/19/2014 1:50 PM, David Thiel wrote: > Interesting, I can't seem to replicate it here. It doesn't seem like > MAKE_JOBS_UNSAFE would apply, but perhaps try that? > > On 02/19, Chad J. Milios wrote: >> there seems to be a timing issue. can anyone else please confirm this >> problem is happening? I haven't gone ahead and tried any non-default >> values of vfs.timestamp_precision. >> >> make package >> fails 26/30 times >> >> make && sleep 1 && make package >> succeeds 50/50 times >> >> Thanks in advance. >>