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:
[0m[31m[1mLinking CXX executable eqsl [0m[ 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
signature.asc
Description: OpenPGP digital signature
