On Thursday 10 November 2011 19:09:28 Luca Barbato wrote:
> On 11/5/11 1:58 AM, Kacper Kowalik wrote:
> > I'd like to ask that we enable verbose building by default. I have
> > cmake-utils.eclass in mind, because it's dead easy there, but there's a
> > lot of packages that support things like "make V=1" or "make VERBOSE=1"
> > too.
> >
> > I've seen too many bugs reports today that gave me cute, colorful
> > build.logs and almost no information about underlaying bug...
>
> That could be done, but I'd advise to make sure our users know that the
> could have a quiet/silent output from portage.

if you want quiet portage output, use something like --quiet when running
emerge. the verbosity of the build output isn't really an issue imo.
-mike

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 <reavertm@gmail.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,
-DG_DISABLE_DEPRECATED...) easily

On 04/02/2012 03:24 PM, Pacho Ramos wrote:
> 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,
> -DG_DISABLE_DEPRECATED...) easily

We've got a feature request bug about detecting -Werror here:

https://bugs.gentoo.org/show_bug.cgi?id=409955
--
Thanks,
Zac

El lun, 02-04-2012 a las 15:34 -0700, Zac Medico escribió:
> On 04/02/2012 03:24 PM, Pacho Ramos wrote:
> > 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,
> > -DG_DISABLE_DEPRECATED...) easily
>
> We've got a feature request bug about detecting -Werror here:
>
> https://bugs.gentoo.org/show_bug.cgi?id=409955

But that is the bug I was also waiting for , the problem is that it
needs verbose output :|