From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 23:42:50 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 289165CD for ; Sat, 24 Nov 2012 23:42:50 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by mx1.freebsd.org (Postfix) with ESMTP id B034C8FC12 for ; Sat, 24 Nov 2012 23:42:49 +0000 (UTC) X-AuditID: 1209190f-b7f636d00000095b-2e-50b15b7851a3 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 23.06.02395.87B51B05; Sat, 24 Nov 2012 18:42:48 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id qAONgmru024714; Sat, 24 Nov 2012 18:42:48 -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 qAONgjZE001415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 24 Nov 2012 18:42:46 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id qAONgids014618; Sat, 24 Nov 2012 18:42:44 -0500 (EST) Date: Sat, 24 Nov 2012 18:42:44 -0500 (EST) From: Benjamin Kaduk To: Garrett Cooper Subject: Re: strange buildworld failure In-Reply-To: <7C31A420-1072-4EB7-A83B-D14195434A16@gmail.com> Message-ID: References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> <50B0B33F.4060802@FreeBSD.org> <50B0EC5B.1080104@gmx.com> <7C31A420-1072-4EB7-A83B-D14195434A16@gmail.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+NgFvrKIsWRmVeSWpSXmKPExsUixG6nrlsRvTHA4MJTFYs5bz4wWeyetZ/Z Yv33ZYwOzB4zPs1n8dg56y67x937C5kCmKO4bFJSczLLUov07RK4Mpq2GxY08lRcv3uNrYFx M2cXIyeHhICJxK7XH1ghbDGJC/fWs4HYQgL7GCU2rbHtYuQCsjcwStydd4YJInGCSaLhuA5E ooFRYtryxewgCRYBbYl5L94wgthsAioSM99sBJskIqAucenAFrAaZoFsiY9zZgAN4uAQBoof PS0EEuYUsJX4dOkCWDmvgIPEmd9NTBDz7zJJbJjxGOw6UQEdidX7p7BAFAlKnJz5hAVipqXE uT/X2SYwCs5CkpqFJLWAkWkVo2xKbpVubmJmTnFqsm5xcmJeXmqRrolebmaJXmpK6SZGUOhy SvLvYPx2UOkQowAHoxIPb+KZ9QFCrIllxZW5hxglOZiURHlNozYGCPEl5adUZiQWZ8QXleak Fh9ilOBgVhLhtVYFyvGmJFZWpRblw6SkOViUxHmvptz0FxJITyxJzU5NLUgtgsnKcHAoSfAW gQwVLEpNT61Iy8wpQUgzcXCCDOcBGt4PUsNbXJCYW5yZDpE/xagoJc7bA5IQAElklObB9cJS yytGcaBXhHkXgVTxANMSXPcroMFMQIOfzl4HMrgkESEl1cBY7+K9UVJe763mx6sn/Mxv6d9o nMNjldy2Q//k8sxpaRk8xiXpp757Sn98UcfhFqJde+ED5zqH+K+mkT9yzrBHLbdxtk2dwSsY kbpUt0bt9+9E0/0zGxuMfb9UJbE/2GmXsuq10r7rT7+d23688cKn20GGO/bbV0xkezlz+oen r/PKc2tv9akrsRRnJBpqMRcVJwIAaqqKdwgDAAA= 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 23:42:50 -0000 On Sat, 24 Nov 2012, Garrett Cooper wrote: > On Nov 24, 2012, at 11:48 AM, Benjamin Kaduk wrote: > >> On Sat, 24 Nov 2012, Nikos Vassiliadis wrote: >> >>> 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. > > The more likely explanation is that one of the parallel threads died > because of enomem, enospc, or a number of other reasons, and it was some > time earlier on in the compile. Stating that it was a build dependency > issue is probably not a wise idea at this time as we do not have enough > data (logs, no -d A required) to substantiate that claim. The point I was trying to make is that a full build log should be sufficient to debug; 'make -d' magic is unlikely to be necessary. Sorry if it came out wrong. -Ben