[tools-issues] [Issue 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 User mechtilde changed the following: What|Old value |New value Status|RESOLVED |CLOSED --- Additional comments from [EMAIL PROTECTED] Thu Nov 6 21:15:34 + 2008 --- close the invalid 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 User terrye changed the following: What|Old value |New value Status|NEW |RESOLVED Resolution| |WONTFIX --- Additional comments from [EMAIL PROTECTED] Fri Sep 14 17:50:14 + 2007 --- Since posting this, I have infact moved to a standard build for development and testing, for the reasons that I describe in: http://wiki.services.openoffice.org/wiki/Ubuntu_Build_in_a_VMware_Appliance And given that the only cost of avoiding the hassle of usingthe tarball is to remember to kick off the build all, then I still don't understand if and why anyone should us the tarball. But yes, please mark this one as cleared. It serves no purpose leaving it as New - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 User vg changed the following: What|Old value |New value Assigned to|vg|terrye --- Additional comments from [EMAIL PROTECTED] Fri Sep 14 10:56:13 + 2007 --- I think the problem is cleared - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 --- Additional comments from [EMAIL PROTECTED] Fri Sep 14 10:55:06 + 2007 --- . - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 --- Additional comments from [EMAIL PROTECTED] Mon Jan 15 06:26:29 -0800 2007 --- @terrye: the idea of the tarballs is: you leech sources+solver tarballs. If everything is in place, you don't need to build the whole office through, but may work with modules of interest right away. Just configure, make changes, build them (or what should be built), deliver - and you can pack the install set in instsetoo. That is the idea. Of cause, it might be faster to build everything by yourself, but that was not always so. I do not have any statistics about how many developers use solver tarballs. "Also if you are using an ooo-build variant then you then have to worry about the interoperability of rebuilding your module which will be patched against the modules that you are defaulting from the standard solver." - Not sure that I understand the problem. If the solver is baseline-conform, it is compatible to your builds, so the should be no problem with mixed binaries in the solver. Of cause, if your changes are incompatible, you should rebuild all dependent modules. - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 --- Additional comments from [EMAIL PROTECTED] Sun Jan 14 04:12:28 -0800 2007 --- @vg: Thanks for your constructive comment. I am now getting a better handle on the whole environment for delevelopers. Yet what I still cannot understand is the value of the solver tarball relative to the promenance you give it on your downloads site. If I am using CCACHE then the rebuild time for a new dot release is only a couple of hours -- which for most people is less significant then having to download what is approaching 1Gbyte. Also if you are using an ooo-build variant then you then have to worry about the interoperability of rebuilding your module which will be patched against the modules that you are defaulting from the standard solver. So the bottom line is that I still don't see how it is of use to a typical OOo developer. Have you yourselves any idea what % of developers use the solver tarball? - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 --- Additional comments from [EMAIL PROTECTED] Fri Jan 5 04:56:02 -0800 2007 --- @vg: providing the configuration of our solver builds makes it more clear that these tarballs are upward compatible, it helps understanding the issues around it. Get more transparancy helps in most cases and does not confuse. - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 --- Additional comments from [EMAIL PROTECTED] Fri Jan 5 04:26:14 -0800 2007 --- @mh: "should be the reference which should used for builds using solver tar balls" - what for? Our tarballs are upward compatible, we are interested in all compiler flavours, especially in newest, if they proven working. Why should we confuse the developers with our environment? - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 --- Additional comments from [EMAIL PROTECTED] Fri Jan 5 04:20:23 -0800 2007 --- @terrye:"...Nonetheless for the solver builds to be usable you need to know the context that they we build in..." I disagree. The concept is - you use YOUR machine with YOUR set of tools to build the OOo.We deliver baseline-conform tarballs, so if you were able to build the OOo from scratch at least one time, there should be no problem to use solver tarballs. Just use your old configure commando to set up the environment, and the unpacked solver tarball as regular solver. Of cause, the minors of tarballs and sources should be same... We want the community to be free in choice of tools. Of cause, there are some restrictions and they are to find in the general description. We cannot nail down the community with firm configuration also because of backward compatibility: we use tweaked environment for full baseline-conform builds, and simplified configure procedure for final tests. I think, that a log from simplified configure would not help you, and a general batch would be possible only for one configuration, while we want the OOo to be buildable on a vast variety of machines. "what Linux release and version in the case of Linux": SuSE 7.3 "what g++": 3.4.1 "what projects were build and at what revision": obviously all OOo projects at the same revision (marked in the name of the tarball) ... "Otherwise you have no basis to know that the solver tree will interoperate with your configuration." - You have, if you have any configuration at all (for the minor) - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 User mh changed the following: What|Old value |New value Assigned to|mh|vg --- Additional comments from [EMAIL PROTECTED] Thu Jan 4 04:49:29 -0800 2007 --- http://wiki.services.openoffice.org/wiki/Compiler_versions_used_by_port_maintainers_and_release_engineers should be the reference which should used for builds using solver tar balls. vladimir please confirm. - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 --- Additional comments from [EMAIL PROTECTED] Sun Dec 31 14:42:51 -0800 2006 --- Nonetheless for the solver builds to be usable you need to know the context that they we build in: what Linux release and version in the case of Linux; what g++ compiler version was used; what projects were build and at what revision ... Otherwise you have no basis to know that the solver tree will interoperate with your configuration. At least you should include in it your make.log and which layered component versions (e.g. by including a g++ --v output) are used. Otherwise it is in practice unusable and you would do everyone who is attempting to build a favour by not wasting their time, and removing the public reference to the solver tarball. - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 User mh changed the following: What|Old value |New value Assigned to|rene |mh Ever confirmed| |1 Status|UNCONFIRMED |NEW Target milestone|--- |OOo 2.x --- Additional comments from [EMAIL PROTECTED] Tue Oct 10 09:16:15 -0700 2006 --- reassign to myself - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 User st changed the following: What|Old value |New value CC|''|'st' Summary|Using Solver: obtaining / |Using Solver: obtaining / |maintaining logfiles of re|maintaining logfiles of re |ference build |ference build Subcomponent|configure |solenv - 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 70256] Using Solver: obtaining / maintaining logfiles of reference build
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 Issue #|70256 Summary|Using Solver: obtaining / maintaining logfiles of refe |rence build Component|tools Version|OOo 2.0.3 Platform|All URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|ENHANCEMENT Priority|P3 Subcomponent|configure Assigned to|rene Reported by|terrye --- Additional comments from [EMAIL PROTECTED] Tue Oct 10 01:32:58 -0700 2006 --- I want to use the OOC680_m7 reference source and solver to rebuild OOo after minor tweaks to one of the modules (basic). I want to minimise my start-up time in doing so and have so far failed. One of the key issues here is that lack of documentation on what the basis for creating the OOC680 (or any future solver tarball) is -- that is what was the reference Linux installation, what was that actual configration (gcc version...), etc. Whilst http://tools.openoffice.org/dev_docs/build_linux.html does provide a general discription, it doesn't provide this firm configuration data making it difficult for developers to replicate the solver environment simply. It would REALLY make life so much easier if as standard practice the solver tarballs were created from a script capable of being run as a *single* batch command, and the output (1&2) sent to a logfile (or better logfile per individual step). These logfiles should be maintained in the solver tree and hence also downloadable. This script should start with the clean-out of all the unxlngi4.pro directories, followed by the configure, bootstrap and build --all. This simple process would enable developers to compare their component versions, options, etc against the solver baseline and trace variations in the build against a solver baseline, and also determine where deviations against the reference solver build were occuring. Also it would be useful if you specfied what your actual Linux for the build was as this information is not listed by the configure script. For developers with limited time, it is easier to replicate your rig than to debug their own. - 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]