Date: Fri, 20 May 2016 20:29:36 -0600 From: Ian Lepore <ian@freebsd.org> To: "Simon J. Gerraty" <sjg@juniper.net>, Bryan Drewery <bdrewery@freebsd.org> Cc: arch@freebsd.org Subject: Re: Build -j target tags and command output Message-ID: <1463797776.1180.357.camel@freebsd.org> In-Reply-To: <77472.1456528808@kaos.jnpr.net> References: <56D0CD68.606@FreeBSD.org> <77472.1456528808@kaos.jnpr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2016-02-26 at 15:20 -0800, Simon J. Gerraty wrote: > Bryan Drewery <bdrewery@freebsd.org> wrote: > > I'm looking for opinions on whether we should keep or remove the -- > > Keep. > > Without them it is virtually impossible to identify which job > produced > certain output. > > Even with them, the log from a parallel hirerarchical build can get > confusing - especially when multiple makes are writing at the same > time. > But you are still better off with some clues. > > > Removing them would yield potentially hard-to-debug failures since > > the > > Yes, pls don't do that. > > > failed command could be anywhere. At least the 'make stopped' > > error > > that follows would print the directory. There is an interesting > > feature > > Yes, but generally the exciting stuff that caused the stoppage is > earlier in the log. > The --- lines allow use of scripts to demux the output. > Are any such scripts available? -- Ian (catching up on really old mail)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1463797776.1180.357.camel>