On Wed, Nov 30, 2011 at 05:59:33PM -0800, Garrett Cooper wrote: > On Wed, Nov 30, 2011 at 5:43 PM, Alexander Best <arun...@freebsd.org> wrote: > > On Wed Nov 30 11, Garrett Cooper wrote: > >> On Wed, Nov 30, 2011 at 4:25 PM, Alexander Best <arun...@freebsd.org> > >> wrote: > >> ? ? pmake sucks as far as diagnostic output is concerned when compared > >> with gmake. I'd rather not have to fish through with -j1 (if I'm lucky > >> and it's not a race) to determine what directory created the "Error > >> Code" output. With the printouts discussed here, at least you have a > >> chance at determining what the issue was. > >> ? ? Maybe it's just me, but I like noisy builds -- otherwise the > >> amount of time I have to spend root-causing the issue becomes > >> expensive. [...] > Otherwise diagnosing issues becomes a PITA with -j > 1 (with pmake I > have to start using some serious grep'ing, and if I'm lucky I can find > the source of error).
Well its a PITA mostly because we disabled Pmake's -j "job-markers" back in 1998 (r41151). If you build with 'make -v -j>1' you get much more debugable output. bmake (NetBSD's make) is even nicer in this regard. I was *amazed* when I joined $WORK and a '-j16' build was debugable. -- -- David (obr...@freebsd.org) _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"