[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User hjs changed the following: What|Old value |New value Status|VERIFIED |CLOSED --- Additional comments from h...@openoffice.org Tue Nov 17 10:07:27 + 2009 --- . - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User hjs changed the following: What|Old value |New value Status|RESOLVED |VERIFIED --- Additional comments from h...@openoffice.org Thu Oct 8 14:56:36 + 2009 --- reviewed the changes, had a look at the output and it still builds - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Tue Oct 6 12:33:17 + 2009 --- Ause asked me to fix a few little issues, and told me that overhauled build.pl recently. So I'm going to rebase the CWS to m61, then fix the minor issues, and then we can get that thing integrated ... So, hands off please :) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User fs changed the following: What|Old value |New value Assigned to|thb |hjs --- Additional comments from f...@openoffice.org Tue Sep 29 07:10:21 + 2009 --- fs-hjs: please verify in CWS buildverbosity - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User fs changed the following: What|Old value |New value Status|STARTED |RESOLVED Resolution| |FIXED --- Additional comments from f...@openoffice.org Mon Sep 28 07:36:37 + 2009 --- okay, built on all of Sun's standard platforms, on all verbosity levels. As said above, the output of the normal and quiet leve are pretty close together, something I'm not really happy with, it kind of makes the third level useless. However, I think the current version is a big improvement already. Also, this is a moving target, anyway, and subject to incremental improvements, so ... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Mon Sep 28 07:37:05 + 2009 --- fs-thb: I'd set the CWS to ready-for-QA, if you agree. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Mon Sep 28 14:50:51 + 2009 --- @fs: pretty please! :) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User thb changed the following: What|Old value |New value CC|'fs,kr,mh,rene,rt,thb'|'fs,hjs,kr,mh,rene,rt,thb' --- Additional comments from t...@openoffice.org Mon Sep 28 19:45:02 + 2009 --- Almost there. One additional commit, fixing my spurious recursive macro def in settings.mk plus a dmake warning there; and an extraneous ls for app targets. @ause: would you want to review/verify this, you seem to be the QA rep? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Mon Sep 28 20:20:06 + 2009 --- Plain vanilla build log file: ~50MB. Current buildverbosity quiet-mode build log: ~4MB. !! thb high-fives fs !! Some more stats: build log has 54117 lines, $find ooo/ -name *.cxx -or -name *.c -or -name *.idl | nl | tail 23959 ... So we still roughly log around two lines per input file on average; of course external libs/helpcontent2/officecfg still blather along rather verbosely; a --with-system-libs build should improve on that quite a bit; and then I guess we start to enter the world of dimishing returns. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Thu Sep 17 07:56:02 + 2009 --- fs-thb: With the current solenv, slideshow/source/engine/smilfunctionparser.cxx doesn't compile here on unxlngi6, complaining as follows: /cws/so-cwsserv02/buildverbosity/DEV300/unxlngi6/inc.m58/boost/spirit/debug /impl/parser_names.ipp:397: warning: declaration of 'trace_node' shadows a member of 'this' The compiler is absolutely right here - however, this does *not* happen when verbose is default (i.e. not set), but only for dmake verbose=true or dmake verbose=false. Did you encounter any such problem? /me's puzzled ... I could fix the problem in boost (as said, the compiler is right in complaining), but I would like to understand why this happens with default verbosity only - this sounds like a a strange side effect of our changes. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Thu Sep 17 09:01:18 + 2009 --- Ah! http://svn.services.openoffice.org/ooo/tags/DEV300_m58/slideshow/util/makefile.pmk In slideshow, if VERBOSE or verbose are defined, this is passed as -DVERBOSE to the compiler. Thorsten, somehow I assume svn blame would tell me this is yours :) Anyway, this explains why this particular problem is triggered only in quiet and verbose mode, so it's nothing broken in solenv, but simply a boost-warning which so far nobody stumbled upon. I'll fix that in module boost, and also slideshow/makefile.pmk to respect VERBOSE=FALSE. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Thu Sep 17 13:21:29 + 2009 --- @fs: hehe, of course you're right - but I was _first_ with using verbose=t, for the record! :) Other than that, I'm probably fine with the quiet vs. normal changes; did I mention I chiefly only care for quiet mode? ;) Except for the boost changes, do we have a state worth integrating now? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Thu Sep 17 20:53:31 + 2009 --- okay, record written down :) Personally, I'd probably also use the quiet mode, but that's not the question here, we need to balance various needs, /me thinks. I have some more local uncommitted changes, and will do a complete build on all our standard platforms on all different verbosity levels - just to be sure. The slideshow thingie made me think it's better to have tested all three levels on all platforms ... So, if you can wait just a few more days ... :) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Wed Sep 16 07:59:35 + 2009 --- I have a few local patches to address the above issues (/me thinks), plus some more silencing. Will build on some platforms before committing this. fs-thb: You made some output dependent on $(COMMAND_ECHO)==, which means it is now only shown in full-verbosity mode, and the normal and the quiet mode don't differ too much anymore. Was this intentional? Just wondering - having already heard people saying something like this is nonsense, I need all that output, we probably shouldn't make the normal mode *too* quiet ... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Wed Sep 16 14:01:42 + 2009 --- @fs: frankly, I don't see the point in quiet vs. normal mode anyway, currently - if normal mode is not echoing compiler calls, why should it echo file modes, or libmgr calls?! For me, only two modes make sense: a) just tell me which file you're processing b) tell me everything you can But before getting bogged down with discussing fringe details again endlessly, I guess the easiest solution (_iff_ this happens to be controversial), is to default to a mode that is as close as possible to the state before (I guess that would be verbose mode now), and let people configure to their likings. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Wed Sep 16 18:54:31 + 2009 --- @thb: Well, I don't really want to argue the necessity of three different modes - I'd have a hard time, too. But this three modes approach was decided quite a while ago - there's some GullFOSS entry by Rüdiger where he explains this. Finally, it really doesn't matter whether we have 2 or 3 or 13 modes, as long as a simple environment variable allows you to switch. So, if you do not have strong objections, I will modify your patch so that the normal mode has some more output, again (but much less than before). This a) makes us adhere to the 3-mode concept decided elsewhere and b) makes it easier for some people to accept the normal mode. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Tue Sep 15 11:11:55 + 2009 --- ah, ok. well, the hard part surely is to find all the places that _are_ hitting already-exising paths; or should we take the lame solution add @@ to _all_ calls? I'd say the latter. On the other hand, this is a moving target, anyway, and nobody hinders us to incrementally fix those places later, once the infrastructure is present in MWS. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Mon Sep 14 15:56:03 + 2009 --- thanks for those changes! about the mkdir-thingie: prefixing the lines with @@ should help. (Ever read http://svn.services.openoffice.org/ooo/tags/DEV300_m58/dmake/man/dmake.nc? I found this highly useful :) Will have a look at the rest as time permits. For the moment, I will probably go to resync to m58, I expect some conflicts with Ause's kick4nt changes ... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Mon Sep 14 19:53:39 + 2009 --- about the mkdir-thingie: prefixing the lines with @@ should help. ah, ok. well, the hard part surely is to find all the places that _are_ hitting already-exising paths; or should we take the lame solution add @@ to _all_ calls? Will have a look at the rest as time permits. For the moment, I will probably go to resync to m58, I expect some conflicts with Ause's kick4nt changes ... Ugh. What a perfect timing then ... ;) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User thb changed the following: What|Old value |New value Assigned to|hjs |thb Target milestone|DevTools |OOo 3.3 --- Additional comments from f...@openoffice.org Wed Sep 2 07:01:31 + 2009 --- fs-thb: ping. I committed all my changes, which reduced the output of a complete build (SO, not OOo) on Linux from 54MB to 22MB. And hey, my mouse keeps moving smoothly when I run a build in a console directed to a X server over a DSL line ... --- Additional comments from t...@openoffice.org Fri Sep 11 22:11:53 + 2009 --- Sooo - committed a load of changes, that gets us fairly close to my goal of having _exactly_ one line per file processed, in quiet mode. Like this, the build looks slow, and people actually get an impression _which_ files take a long time to compile; additionally, warnings stick out like a sore thumb. Things I'm not yet happy with: * about a gazillion spews of mkdir: cannot create directory `../../unxlngx6/misc/desktopshare/': File exists, in ooo-build, I've fixed that for a few especially annoying places via '@-$(MKDIR) $(@:d) $(PIPEERROR) cat - /dev/null', but that does not really scale ... * some (java?) zip targets are still tracing the files added * for me, in settings,mk, the 'VERBOSE=$(eq,$(VERBOSE_IS_FALSE),t FALSE TUE)' gives this: dmake: /builds/ooo/buildverbosity/solenv/inc/settings.mk: line 991: Error: -- Detected circular macro [VERBOSE] * building those version.c file per shared library object do not yet hide compiler calls - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User thb changed the following: What|Old value |New value Status|NEW |STARTED --- Additional comments from t...@openoffice.org Fri Sep 11 22:12:48 + 2009 --- I guess this has really started now ... ;) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Tue Sep 1 10:11:11 + 2009 --- @fs: deal. please ping me when done. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User fs changed the following: What|Old value |New value CC|'kr,mh,rene,rt,thb' |'fs,kr,mh,rene,rt,thb' --- Additional comments from f...@openoffice.org Mon Aug 31 10:05:24 + 2009 --- being annoyed by the extensive noise produced by a simple build, I embarked upon this, too. Unfortunately *after* finding this issue here ... Anything, perhaps we can resurrect the issue, and combine our approaches. I have a patch (to be attached) which - fixes various .mk files in solenv/inc to *not* echo the current command, in particular calls to mkdepend, various compilers on the different platforms, and the resource compiler (the approach for this is identical to setting QUIET_BUILD to @, just my variable has another name) - fixes mhid.pl to not echo the command unless -verbose is given - fixes the resource compiler to not echo all the useless stuff until -verbose is given - fixes solenv/inc/*.mk to pass -verbose to the resource and the HID compiler As you see, I mainly concentrated on reducing the verbosity of stuff which IMO belongs into the debug level (verbose=true). I did not spend any work into implementing a quiet level. What I'd like to see is a combination of the current patches (implementing the quiet mode) with my patch (moving a lot of output to a dedicated verbose mode). I also do not have a solution for the echo the failing command in case of an error problem, but I'd say that this could be postponed ... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Mon Aug 31 10:06:27 + 2009 --- Created an attachment (id=64452) patch for moving a lot of the noise from verbosity level 'normal' to debug verbosity level - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Mon Aug 31 19:03:20 + 2009 --- @fs: yay, you rock - this nicely complements my stuff :) Additionally I have a patch floating around for silencing checkdll idlc some more - but why not throw this together into a cws? @releng: ok for going after this, ignoring the error output problem for the while, as this seems to be blocking the issue indeterminantly? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from f...@openoffice.org Tue Sep 1 04:37:19 + 2009 --- @thb: I extended my patch yesterday, also silencing idlc :), and the script particle compiler, and some more output during normal compiling. In hurrying obedience, I created a CWS buildverbosity last week. I suggest I'll commit my stuff later this day, and you can add your quiet-mode patches on top of that. As for releng: Ause said something like Just Do It (TM) to me, so just let's go ahead, as long as nobody complains. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User thb changed the following: What|Old value |New value Attachment is patch| |Created an attachment (id= | |62354) Make build.pl shut | |up as well... --- Additional comments from t...@openoffice.org Mon May 18 20:19:15 + 2009 --- Created an attachment (id=62354) Make build.pl shut up as well... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User rt changed the following: What|Old value |New value Target milestone|--- |DevTools --- Additional comments from r...@openoffice.org Fri May 15 07:55:12 + 2009 --- Concerning the 'main' patch: I do not know whether this $(QUIET_BUILD) thing has any side effects, but for me it looks good. Anyone tested it yet? Ause, what do you think? Thanks, Thorsten, for the effort. For the concept: We once proposed and started to introduce three levels of verbosity: default: no extra configure option environment variable VERBOSE unset silent: configure option '--disable-verbose' environment variable VERBOSE=FALSE verbose: configure option '--enable-verbose' environment variable VERBOSE=TRUE This does not fit the to part of the patch concerning settings.mk +.IF $(VERBOSE)== $(verbose)== +QUIET_BUILD*=@ +.ELSE +QUIET_BUILD*= +.ENDIF + Thorsten, do I understand you correctly that your changes are meant for the default case? If so, we should conditionalize as .IF $(VERBOSE)==TRUE QUIET_BUILD*= .ELSE QUIET_BUILD*=@ .ENDIF If instead we only want it for the 'silent' case that of course should look the other way round, set 'QUIET_BUILD*=@' if and only if $(VERBOSE)==FALSE - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Fri May 15 13:46:49 + 2009 --- @rt: yeah, I already stated my preferred default ;) - but let's not get bogged down on this; I actually don't care at all what the default is, as long as I can configure it easily. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Fri May 15 13:48:20 + 2009 --- oh btw, the original patch from Michael is used in ooo-build since about a year or so, without any known side effects. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User thb changed the following: What|Old value |New value Attachment is patch| |Created an attachment (id= | |62277) More quiet build --- Additional comments from t...@openoffice.org Thu May 14 21:56:16 + 2009 --- Created an attachment (id=62277) More quiet build - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from t...@openoffice.org Thu May 14 22:04:42 + 2009 --- I admittedly don't like the 'dmake -s' approach *at all*, not the least because issueing dmake in a subdir will get me the full output again I (and probably most other devs) do that a lot. And no, please no alias tricks again, let's move away from that as well... ;) Additionally, this still is *much* too verbose for me, the @echo s are especially useless in quiet mode. Not to speak of transex3, rsc, etc. logging kLocs of output in the plain, normal, successful case. :) So, attached patch hopefully catches ~all targets; another piece to work on is definitely build.pl, the dir printing # process logging in multi-processor builds are a bit clutterative, too. @rene releng: let's not fight over defaults here, please; the whole thing should have a configure option be done with it... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org For additional commands, e-mail: issues-h...@tools.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Tue Nov 18 14:49:21 + 2008 --- Created an attachment (id=58084) An other approach for quiet builds: use dmake option '-s' - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Tue Nov 18 14:55:40 + 2008 --- 'dmake -s' gives what Michel's patch does, but it also lacks showing the failing command. Will keep searching ... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User thb changed the following: What|Old value |New value CC|'kr,mh,rene,rt' |'kr,mh,rene,rt,thb' --- Additional comments from [EMAIL PROTECTED] Wed Sep 24 11:21:02 + 2008 --- Hm. No progress for 3 quarters - is there _any_ feasible, generally applicable solution to the echo when failed problem? If not, I'd suggest taking the patch as-is (I, too, prefer the quiet build). For the remote builders like rene, if the default stays at verbose, this won't harm you at all, and those on a local shell can surely do a cd target dir; dmake verbose=t on errors, no? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Wed Sep 24 11:48:07 + 2008 --- I'd still like to take this one, just had other priorities during past month. I hoped to come back to 'shutup*' childworkspaces when our migration to svn is finished. Nevertheless, if you like to take over, feel free to do so. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Wed Sep 24 11:57:20 + 2008 --- thb: you've seen the concept of three verbose levels as described in issue 84263 ? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Wed Sep 24 20:31:09 + 2008 --- @rt: yep, loosely followed that. As a developer, being one of the main targets of build system output, I concur with Kay - I just need info about the file that currently gets compiled, no frills. Tar output install sets are minor issues IMO, as they represent only fractions of normal build logs. What I'm after is, the patch here improves things a lot for me (it might even do what you suggested for the verbose=false case - *not* logging anything per compiled file is clearly not want I want), so why not taking this as a step in the right direction integrate it (or put it into one of the *shutup CWS)? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Mon Sep 22 21:54:16 + 2008 --- *** Issue 93814 has been marked as a duplicate of this issue. *** - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User thb changed the following: What|Old value |New value Attachment is patch| |Created an attachment (id= | |56738) The meat from the d | |upe issue --- Additional comments from [EMAIL PROTECTED] Mon Sep 22 21:58:07 + 2008 --- Created an attachment (id=56738) The meat from the dupe issue - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Thu Dec 20 14:27:47 + 2007 --- ok, here some comments from my side: ideally i would like to have three levels of verbosity: quiet, verbose and debug. quiet in my imagination would match the preference of kr, just printing a short note about what's going on. verbose would be similar to what we have now, except for some flooding we have now (e.g. unpacking). debug would show everything and can probaly be achived in combination with -v option of dmake. for quiet mode, it would increase the usability (if not be required) if there is some additional information, normally the failing command line, on error. otherwise a failing build in quiet mode would require the builder to do the failing step again in a different build mode and hope that the error reappears... the QUIET_BUILD=@ approach alone may help to reduce the output of the verbose mode to sensible level. the $(silent_cmd) || echo $(silent_cmd) approach may face the problem that it's not possible inside reciepts (the actual target lines) to set variable in the common way and an other question, who volunteers to do that? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Thu Dec 20 14:48:23 + 2007 --- ideally i would like to have three levels of verbosity: quiet, verbose and debug. quiet in my imagination would match the preference of kr, just printing a short note about what's going on. verbose would be similar to what we have now, except for some flooding we have now (e.g. unpacking). debug would show everything and can probaly be achived in combination with -v option of dmake. Yeah. And please leave the default at verbose then :) People who want it quiet can set it. for quiet mode, it would increase the usability (if not be required) if there is some additional information, normally the failing command line, on error. Indeed. otherwise a failing build in quiet mode would require the builder to do the failing step again in a different build mode and hope that the error reappears... Which is not possible on remote, automatic builds without any interaction anywway, so... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Tue Dec 18 15:20:30 + 2007 --- Michael, I think providing the command line in case of an error is quite helpful ... and may allow to convince the sceptical voices. Also I would like to see the same approach for build-bots as well as hand crafted builds. Introducing such a variable is IMHO in general doable, the problem I see more or less lies in our not so transparent build system ... ;-) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User mmeeks changed the following: What|Old value |New value CC|'kr,rene,rt' |'kr,mh,rene,rt' --- Additional comments from [EMAIL PROTECTED] Tue Dec 18 15:35:43 + 2007 --- I think providing the command line in case of an error is quite helpful Sure - it's also not difficult at all - but it is esthetically challenging - consequently, it's necessary to get release-engineering to comment on the style of makefile rule they would prefer. I propose: $(OBJ)$/%.obj : %.cpp maps to: OBJ_OBJ_CPP = $(QUIET_BUILD) $(CAPTURE_COMMAND) $(CXX) $(ACT_PCH_SWITCHES) $(CFLAGS) $(INCLUDE) $(CFLAGSCXX) $(CFLAGSCXXSLO) $(CFLAGSSLO) $(CDEFS) $(CDEFSSLO) $(CDEFSMT) $(!eq,$(EXCEPTIONSFILES),$(subst,$@, $(EXCEPTIONSFILES)) $(LOCAL_EXCEPTIONS_FLAGS) $(GLOBAL_EXCEPTIONS_FLAGS)) $(CFLAGSAPPEND) $(CFLAGSOUTOBJ) $(SLO)$/$*.o $(CFLAGSINCXX)$(PWD)$/$*.cxx $(CAPTURE_OUTPUT) ... @$(OBJ_OBJ_CPP) || echo Failed command $(OBJ_OBJ_CPP) or somesuch ? - the problem being that there is already a fair amount of command duplication out there, or, even use some form of this pattern to try to reduce the rampant (presumably fragile) cut paste in rules.mk. Either way - there are now ~4 questions wrt. how to do this for releng, as I say, it seems conceptually easy to do, albeit some amount of typing, but this is not our code to maintain, so proceeding without input seems pointless: Martin ? Heiner ? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Fri Dec 14 09:45:41 + 2007 --- Weelll ... printing the command on failure is relatively do-able I guess, but would need some intermediate variable to hold the command-line to avoid cut/paste. Having said that - how necessary is this for developer builds ? for some automated build-bot style building perhaps but for personal builds ... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User rt changed the following: What|Old value |New value CC|'kr' |'kr,rt' --- Additional comments from [EMAIL PROTECTED] Thu Dec 13 08:22:15 + 2007 --- Have you seen issue 84263 ? There we already had some discussion about what degree of verbosity should be default. I plan to work on things like this in CWS shutup2. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User rene changed the following: What|Old value |New value CC|'kr,rt' |'kr,rene,rt' - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 --- Additional comments from [EMAIL PROTECTED] Thu Dec 13 16:36:25 + 2007 --- I was also playing with not echoing compiler command lines, in the spirit I mentioned in 84263 . Also tried to convince Rene :-) , important point basically is, that if anything fails, the causing command line should be echoed, this should likely be true for all commands. Currently we have both, we do echo something as Making bla.o ... as well as the command line, either or should be enough. Personally I would favour a simple compiling bla.cxx ... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 Issue #|84497 Summary|quieten build noise ... Component|tools Version|680m237 Platform|All URL| OS/Version|Linux Status|NEW Status whiteboard| Keywords| Resolution| Issue type|PATCH Priority|P3 Subcomponent|solenv Assigned to|hjs Reported by|mmeeks --- Additional comments from [EMAIL PROTECTED] Wed Dec 12 15:37:48 + 2007 --- So ... of course, sometimes the huge gcc command lines are very useful for debugging, but unfortunately much of the time they simply serve to slow down a build (by churning the console / X server ;-), give a false impression of 'speed', and far worse - hide warnings amid the verbiage. I attach a very simple start to address the issue - comments much appreciated. build VERBOSE=true turns the churn back on: queries: + 'VERBOSE' or 'verbose' ? + is the approach of QUIET_BUILD=@ ok ? it appears to work nicely + is the separator approach ok, or do we want [EMAIL PROTECTED] -- and just use that as a rule ? + any non-obvious anticipated problems ? :-) Thanks. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84497] quieten build noise ...
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497 User mmeeks changed the following: What|Old value |New value Attachment is patch| |Created an attachment (id= | |50266) patch --- Additional comments from [EMAIL PROTECTED] Wed Dec 12 15:38:18 + 2007 --- Created an attachment (id=50266) patch - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
