On Sat, Jul 25, 2020 at 12:22:53PM +0100, Stuart Henderson wrote: > On 2020/07/25 01:07, Klemens Nanni wrote: > > On Mon, Jul 20, 2020 at 08:35:19AM +0200, Landry Breuil wrote: > > > Definitely seconded. Having that feature by default without having knobs > > > to push (or remembering another external obscure command) would be > > > helpful... the only concern being objdir getting bigger :) > > Is that a real concern, though? BUILD_LOGFILE might "blow up" for huge > > builds, but I have no setup to build monsters such as chromium or > > firefox: can anyone tell me how big the entire build log would be after > > redirecting it to a file. > > There are a couple which are 50-100MB but not huge in relation to > work dir sizes. > > > Either ways, I'm still in favour of built-in logs as you say; any other > > porters with feedback on this? After all, this ought to make every > > porter's life easier, not just mine. > > > > Seems totally pointless to me. What's so hard about piping through > portslogger or just plain tee?
Having to remember about it. I've built ports umpteen times with make, only to find out they fail somewhere, and wasting time doing make clean && make 2>&1 | tee build.log. Having it by default (or behind a 'set and forget' mk.conf knob) would definitely help. Landry
