| 1 |
On 11/05/11 21:00, Maciej Mrozowski wrote: |
| 2 |
> On Saturday 05 of November 2011 09:58:00 Kacper Kowalik wrote: |
| 3 |
>> Hi, |
| 4 |
>> I'd like to ask that we enable verbose building by default. I have |
| 5 |
>> cmake-utils.eclass in mind, because it's dead easy there, but there's a |
| 6 |
>> lot of packages that support things like "make V=1" or "make VERBOSE=1" |
| 7 |
>> too. |
| 8 |
>> |
| 9 |
>> I've seen too many bugs reports today that gave me cute, colorful |
| 10 |
>> build.logs and almost no information about underlaying bug... |
| 11 |
> |
| 12 |
> That's usually because users sometimes attach only "relevant" parts of build |
| 13 |
> log (well, relevant according to their taste = last lines, even when they use |
| 14 |
> parallel compilation). |
| 15 |
> Any particular example of bug report with entire build log from cmake-utils in |
| 16 |
> fancy mode, and still being unable to locate the problem? |
| 17 |
> |
| 18 |
> I ask, because we're appending summary just after configure phase to make |
| 19 |
> vorbose logging of whole build process unecessary. |
| 20 |
Yeah take bug 297699 as an example and relavant snippet: |
| 21 |
|
| 22 |
[0m[31m[1mLinking CXX executable eqsl |
| 23 |
[0m[ 22%] CMakeFiles/eqsl.dir/eqsl.cxx.o: In function `callback(char |
| 24 |
const*)': |
| 25 |
eqsl.cxx:(.text+0x192a): undefined reference to `Fl::lock()' |
| 26 |
eqsl.cxx:(.text+0x1ef1): undefined reference to `Fl::unlock()' |
| 27 |
|
| 28 |
As we don't see actual linking we cannot immediately tell what libraries |
| 29 |
were linked and rule out/diagnose as-needed issue. As I cannot even |
| 30 |
reproduce the bug right now I can only rely on clairvoyance to figure |
| 31 |
what happened there... |
| 32 |
|
| 33 |
Cheers, |
| 34 |
Kacper |
Archives