From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 11:44:57 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D93EB1AC for ; Sat, 24 Nov 2012 11:44:57 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8E5F38FC08 for ; Sat, 24 Nov 2012 11:44:57 +0000 (UTC) Received: from [192.168.0.6] (spaceball.home.andric.com [192.168.0.6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 18C435C37; Sat, 24 Nov 2012 12:44:56 +0100 (CET) Message-ID: <50B0B33F.4060802@FreeBSD.org> Date: Sat, 24 Nov 2012 12:45:03 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Benjamin Kaduk Subject: Re: strange buildworld failure References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nikos Vassiliadis , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 24 Nov 2012 11:44:57 -0000 On 2012-11-24 03:38, Benjamin Kaduk wrote: > On Fri, 23 Nov 2012, Nikos Vassiliadis wrote: >> On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: >>>> Also, my src.conf had WITHOUT_CLANG but I deleted it and then I >>>> also deleted /usr/obj when it failed for the first time. But that >>>> didn't work. I am building with -j3. >>> >>> Does it always fail there at usr.bin/ypwhich? >>> It's likely that -j3 is the culprit of why you do not see the actual build >>> error because it might be lost off the screen. Try to restart without -jN. >>> >> >> Thanks, that worked. > > Hmm, buildworld is supposed to be parallel-make-safe. > Perhaps a full log of the failing buildworld (e.g., with script(1)) could > be posted for analysis? Well, either a full log, or the tail of the log, as long as it contains the actual command(s) that failed. Sometimes it can help to search backwards with less, or your favorite editor, for the string "error:", or if there is no such string, searching for other problem indicators. Also, copies of make.conf and src.conf are often essential in finding the cause of the problem. Many build issues are caused by erroneous settings. :)