El sáb, 05-11-2011 a las 21:03 -0600, Ryan Hill escribió:
> On Sat, 5 Nov 2011 21:00:32 +0100
> Maciej Mrozowski <email@example.com> wrote:
> > > I've seen too many bugs reports today that gave me cute, colorful
> > > build.logs and almost no information about underlaying bug...
> > That's usually because users sometimes attach only "relevant" parts of build
> > log (well, relevant according to their taste = last lines, even when they use
> > parallel compilation).
> I think you're confusing build log with build output.
> > Any particular example of bug report with entire build log from cmake-utils in
> > fancy mode, and still being unable to locate the problem?
> > I ask, because we're appending summary just after configure phase to make
> > vorbose logging of whole build process unecessary.
> How are you supposed to debug a compile or linker error without the compiler
> command line?
How all this ended up? It would still be nice to have verbose output
enabled by default (even people being able to use emerge --quiet to
silent it) to check for undesired flags (like -Werror,