enable verbose build whenever it's possible
 

On Sat, Nov 5, 2011 at 2:28 PM, Kacper Kowalik <xarthisius@gentoo.org> wrote:
> Hi,
> 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...

Is there a way to output the verbose log to build.log, but show the
shortened log to the terminal? The non-verbose build is quite useful
for seeing the actual warnings as they fly by rather than the entire
gcc/libtool command, which is often mostly noise.

--
~Nirbheek Chauhan

Gentoo GNOME+Mozilla Team

enable verbose build whenever it's possible
 

On Sat, Nov 5, 2011 at 11:27 AM, Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
>
> Is there a way to output the verbose log to build.log, but show the
> shortened log to the terminal? The non-verbose build is quite useful
> for seeing the actual warnings as they fly by rather than the entire
> gcc/libtool command, which is often mostly noise.
>

And writing to std{out,err} is expensive! ;-)

> --
> ~Nirbheek Chauhan
>
> Gentoo GNOME+Mozilla Team
>
>



--
Fabio Erculiani
http://lxnay.com

enable verbose build whenever it's possible
 

>>>>> On Sat, 05 Nov 2011, 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...

In fact, there's already bug 379497 [1] open for this. Some build
systems might use the variable V for something else, so adding
--disable-silent-rules may be the safer solution.

Ulrich

[1] <https://bugs.gentoo.org/show_bug.cgi?id=379497>

enable verbose build whenever it's possible
 

El sáb, 05-11-2011 a las 09:58 +0100, Kacper Kowalik escribió:
> Hi,
> 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...
> Cheers,
> Kacper
>

I also support this :)

enable verbose build whenever it's possible
 

On Sat, 5 Nov 2011 12:05:15 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:

> >>>>> On Sat, 05 Nov 2011, 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...
>
> In fact, there's already bug 379497 [1] open for this. Some build
> systems might use the variable V for something else, so adding
> --disable-silent-rules may be the safer solution.

Yeah, please use the correct configure opt rather than throwing in
random makevars.

--
Best regards,
Michał Górny

enable verbose build whenever it's possible
 

W dniu 05.11.2011 18:04, Michał Górny pisze:
> On Sat, 5 Nov 2011 12:05:15 +0100
> Ulrich Mueller <ulm@gentoo.org> wrote:
>
>>>>>>> On Sat, 05 Nov 2011, 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...
>>
>> In fact, there's already bug 379497 [1] open for this. Some build
>> systems might use the variable V for something else, so adding
>> --disable-silent-rules may be the safer solution.
Of course --disable-silent-rules is the way to go for autotools based
packages.
>
> Yeah, please use the correct configure opt rather than throwing in
> random makevars.
I don't want to throw any vars blindly to emake. V=1 was just an example
that I've seen in some packages' build systems. It was more like a
proposal to use whatever build system of given package provides.
Cheers,
Kacper

enable verbose build whenever it's possible
 

On Saturday 05 of November 2011 09:58:00 Kacper Kowalik wrote:
> Hi,
> 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'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).
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.

--
regards
MM

enable verbose build whenever it's possible
 

On 11/05/11 21:00, Maciej Mrozowski wrote:
> On Saturday 05 of November 2011 09:58:00 Kacper Kowalik wrote:
>> Hi,
>> 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'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).
> 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.
Yeah take bug 297699 as an example and relavant snippet:

Linking CXX executable eqsl
[ 22%] CMakeFiles/eqsl.dir/eqsl.cxx.o: In function `callback(char
const*)':
eqsl.cxx:(.text+0x192a): undefined reference to `Fl::lock()'
eqsl.cxx:(.text+0x1ef1): undefined reference to `Fl::unlock()'

As we don't see actual linking we cannot immediately tell what libraries
were linked and rule out/diagnose as-needed issue. As I cannot even
reproduce the bug right now I can only rely on clairvoyance to figure
what happened there...

Cheers,
Kacper

enable verbose build whenever it's possible
 

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?


--
fonts, gcc-porting, it makes no sense how it makes no sense
toolchain, wxwidgets but i'll take it free anytime
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

enable verbose build whenever it's possible
 

On 11/5/11 1:58 AM, Kacper Kowalik wrote:

Hi,
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.


lu