On Sat, 24 Nov 2012, Garrett Cooper wrote: > On Nov 24, 2012, at 11:48 AM, Benjamin Kaduk <kaduk_at_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. -BenReceived on Sat Nov 24 2012 - 22:42:50 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:32 UTC