| 1 |
On Sat, 5 Nov 2011 21:00:32 +0100 |
| 2 |
Maciej Mrozowski <reavertm@×××××.com> wrote: |
| 3 |
|
| 4 |
> > I've seen too many bugs reports today that gave me cute, colorful |
| 5 |
> > build.logs and almost no information about underlaying bug... |
| 6 |
> |
| 7 |
> That's usually because users sometimes attach only "relevant" parts of build |
| 8 |
> log (well, relevant according to their taste = last lines, even when they use |
| 9 |
> parallel compilation). |
| 10 |
|
| 11 |
I think you're confusing build log with build output. |
| 12 |
|
| 13 |
> Any particular example of bug report with entire build log from cmake-utils in |
| 14 |
> fancy mode, and still being unable to locate the problem? |
| 15 |
> |
| 16 |
> I ask, because we're appending summary just after configure phase to make |
| 17 |
> vorbose logging of whole build process unecessary. |
| 18 |
|
| 19 |
How are you supposed to debug a compile or linker error without the compiler |
| 20 |
command line? |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
fonts, gcc-porting, it makes no sense how it makes no sense |
| 25 |
toolchain, wxwidgets but i'll take it free anytime |
| 26 |
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |
Archives