From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 19:48:29 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 87EE78F8; Sat, 24 Nov 2012 19:48:29 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.35]) by mx1.freebsd.org (Postfix) with ESMTP id 0BEE88FC12; Sat, 24 Nov 2012 19:48:28 +0000 (UTC) X-AuditID: 12074423-b7fab6d0000008f9-9c-50b12486a0f5 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 31.A5.02297.68421B05; Sat, 24 Nov 2012 14:48:22 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id qAOJmL8t026389; Sat, 24 Nov 2012 14:48:22 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qAOJmI9p027477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 24 Nov 2012 14:48:21 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id qAOJmIDX011861; Sat, 24 Nov 2012 14:48:18 -0500 (EST) Date: Sat, 24 Nov 2012 14:48:18 -0500 (EST) From: Benjamin Kaduk To: Nikos Vassiliadis Subject: Re: strange buildworld failure In-Reply-To: <50B0EC5B.1080104@gmx.com> Message-ID: References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> <50B0B33F.4060802@FreeBSD.org> <50B0EC5B.1080104@gmx.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrIIsWRmVeSWpSXmKPExsUixCmqrNumsjHAYOVKeYslXfsYLea8+cBk sXvWfmYHZo8Zn+azeNy9v5ApgCmKyyYlNSezLLVI3y6BK+PM3QOMBbt5KjZ27WdtYPzM2cXI ySEhYCLxcPkfZghbTOLCvfVsXYxcHEIC+xglZp04CuVsYJQ4dPgRM4Rzgkliz+9nrBBOA6PE g3kPWEH6WQS0Ja7sWg82i01ARWLmm41sILaIgKrEpis7GUFsZgFHidYZ/9i7GDk4hAXUJY6e FgIJcwKZH5YtZQMJ8wo4SDx7HQYSFhL4yigxp9cExBYV0JFYvX8KC4jNKyAocXLmExaIiZYS 5/5cZ5vAKDgLSWoWktQCRqZVjLIpuVW6uYmZOcWpybrFyYl5ealFumZ6uZkleqkppZsYQSHL 7qK8g/HPQaVDjAIcjEo8vAln1gcIsSaWFVfmHmKU5GBSEuVdpbgxQIgvKT+lMiOxOCO+qDQn tfgQowQHs5IIrxFIjjclsbIqtSgfJiXNwaIkznst5aa/kEB6YklqdmpqQWoRTFaGg0NJgjdD GahRsCg1PbUiLTOnBCHNxMEJMpwHaLgySA1vcUFibnFmOkT+FKOilDhvMUhCACSRUZoH1wtL Ka8YxYFeEeZNB6niAaYjuO5XQIOZgAY/nb0OZHBJIkJKqoHRwWUhz0v+lNkB/Bd7fty+WvW9 d97eQI6JNWyLK2N0Oj6uSfscevTQ/L8Bq4+J/srpY7Iz4L/kPu3ipkvrVRXNBWzP271U+7HJ XXLytlkOX4yn9P0qd2YsZvt5j+vaHKbXk4suVRvt8De4nciSdvNG0sO9fHPt22da+bWu12p4 //ZzHb/4K8cnSizFGYmGWsxFxYkA+F78+AQDAAA= Cc: freebsd-current@FreeBSD.org, Dimitry Andric 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 19:48:29 -0000 On Sat, 24 Nov 2012, Nikos Vassiliadis wrote: > On 11/24/2012 1:45 PM, Dimitry Andric wrote: >> On 2012-11-24 03:38, Benjamin Kaduk wrote: >>> >>> 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. :) > > By the way, I tried to add some debugging info with the help of make -d A > or -d g2 but the amount of logging was excessive(the build was ran in a tmux > terminal and the tmux process was using more CPU time than the build itself, > so I canceled). What should I use with "make -d" in order to get some basic > debugging? Or is there another way? Most cases I know of where a parallel make fails and a serial make succeeds are due to incomplete specification of dependencies. This can usually be chased down with just a build log, without extra debugging information. I have only needed to resort to the make debugging outputs when doing more interesting things like custom suffix rules or using the SRCS+OBJS magic provided by the system makefiles in unusual ways. -Ben Kaduk