Date: Sat, 24 Nov 2012 12:45:03 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: Nikos Vassiliadis <nvass@gmx.com>, freebsd-current@freebsd.org Subject: Re: strange buildworld failure Message-ID: <50B0B33F.4060802@FreeBSD.org> In-Reply-To: <alpine.GSO.1.10.1211232138030.2164@multics.mit.edu> References: <50AF3509.7070402@gmx.com> <CAE-mSO%2BD-KCbJrYrV4c%2BST4Jz0YNRKWnZD6gode2dMGP33=qWA@mail.gmail.com> <50AFED32.5020005@gmx.com> <alpine.GSO.1.10.1211232138030.2164@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B0B33F.4060802>