Date: Sat, 24 Nov 2012 18:42:44 -0500 (EST) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Garrett Cooper <yanegomi@gmail.com> Cc: Nikos Vassiliadis <nvass@gmx.com>, "freebsd-current@FreeBSD.org" <freebsd-current@FreeBSD.org> Subject: Re: strange buildworld failure Message-ID: <alpine.GSO.1.10.1211241841080.2164@multics.mit.edu> In-Reply-To: <7C31A420-1072-4EB7-A83B-D14195434A16@gmail.com> 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> <50B0B33F.4060802@FreeBSD.org> <50B0EC5B.1080104@gmx.com> <alpine.GSO.1.10.1211241445110.2164@multics.mit.edu> <7C31A420-1072-4EB7-A83B-D14195434A16@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Nov 2012, Garrett Cooper wrote: > On Nov 24, 2012, at 11:48 AM, Benjamin Kaduk <kaduk@MIT.EDU> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1211241841080.2164>