From owner-freebsd-current@FreeBSD.ORG Wed Jan 20 23:50:29 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95D88106566C for ; Wed, 20 Jan 2010 23:50:29 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email1.allantgroup.com (email1.emsphone.com [199.67.51.115]) by mx1.freebsd.org (Postfix) with ESMTP id 5C2928FC0C for ; Wed, 20 Jan 2010 23:50:29 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email1.allantgroup.com (8.14.0/8.14.0) with ESMTP id o0KNoPQH069140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 20 Jan 2010 17:50:25 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.4/8.14.3) with ESMTP id o0KNoOPJ077793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 20 Jan 2010 17:50:25 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.4/8.14.3/Submit) id o0KNoOWB077790; Wed, 20 Jan 2010 17:50:24 -0600 (CST) (envelope-from dan) Date: Wed, 20 Jan 2010 17:50:24 -0600 From: Dan Nelson To: Matt Thyer Message-ID: <20100120235024.GE50360@dan.emsphone.com> References: <20100120162326.GD50360@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 7.2-STABLE User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: clamav-milter 0.95.3 at email1.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (email1.allantgroup.com [199.67.51.78]); Wed, 20 Jan 2010 17:50:26 -0600 (CST) X-Scanned-By: MIMEDefang 2.45 Cc: current@freebsd.org Subject: Re: Buildworld failure with -j24 and ZFS on GPT on Core i7-860 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jan 2010 23:50:29 -0000 In the last episode (Jan 21), Matt Thyer said: > 2010/1/21 Dan Nelson > > In the last episode (Jan 21), Matt Thyer said: > > > I typically buildworld with a parallel make of hw.ncpu * 3 which > > > results in -j24 on my new system (Intel Core i7-860, 8GB RAM). [...] > > > Build failure is: > > > > > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 asn1_err.h > > > /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/heim_asn1.h > > > cms_asn1.h rfc2459_asn1.h krb5_asn1.h pkinit_asn1.h pkcs8_asn1.h > > > pkcs9_asn1.h pkcs12_asn1.h digest_asn1.h kx509_asn1.h > > > /usr/obj/usr/src/tmp/usr/include > > > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libasn1.so.10 > > > /usr/obj/usr/src/tmp/usr/lib > > > ln -fs libasn1.so.10 /usr/obj/usr/src/tmp/usr/lib/libasn1.so > > > 1 error > > > *** Error code 2 > > > 1 error > > > *** Error code 2 > > > 1 error > > > *** Error code 2 > > > 1 error > > > > It's much more likely to be a Makefile dependency problem than a ZFS > > bug. You will need to look much farther up in your log to see the real > > error message. Make will wait for the other 23 jobs to finish before > > returning, so what you posted was the output of one of the other jobs, > > plus the output of each parent make as it exits with an error code. > > This was my first thought so I grepped my log for "error" in a case > insensitive way and found nothing. That's why I think that it may be a > file system issue as the line prior to the link is the installation of the > "libasn1.so.10" shared library. I have now installed the same JPSNAP on > another identical hard disk (300GB Seagate SATA) in a UFS only system and > will test again shortly. Since the ln command didn't print an error message itself, it's unlikely to have caused the build to fail. Try searching for "***" or ":" instead. You can try adding -v or -P to your initial make commandline; either will add extra lines to parallel builds that make it easier to tell exactly what make target caused a failure. I don't know if they will cause issues with the buildworld framework, though. Try running "make -j2", "make -v -j2", and "make -P -j2" on the following Makefile to see what the flags do: ( indented lines have leading tabs ) test: test1 test2 test1: @sleep 1 @false test2: @echo "hi I'm a successful target" -- Dan Nelson dnelson@allantgroup.com