On Tue, Jan 31, 2012 at 11:43 AM, Michael Stahl <mstahl@redhat.com> wrote:
hi all,
a recurring problem with remote debugging newbie build problems is that
the default build is silent.
i wonder if it would make sense to change that:
with default configure invocation, build system outputs the full command
to the terminal/log, and there is an explicit configure option to
silence the build.
so when newbies pastebin their broken build, it's much easier for
developers to spot wrong command lines without wasting time writing a
lot of pointless mails and such.
actually for tinderbox builds there could also be advantages (though it
would also make the logs a lot bigger).
One thing that would mitigate the size of the log in that case would
be to hide the 'untar' output, even in verbose mode
(put it is a separate file in misc/logs for instance)
un-tarring of boost, for instance, account for thousands of line of
pointless output in verbose mode...
even better, for gbuild, would be to store the output of each command
in a file (again logs/xxx) and only display it inn case of problem.
this has the added benefit of keeping the whole output together (*)
Norbert
(*) and the added 'benefit' of allowing fairly stable eye-candy like
coloring the output
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.