Re: Request a actual Build for Mac OS
On 11/15/13 4:06 AM, Raphael Bircher wrote: Hi all I'm not able to build with Mac OS X 10.5 anymore. We have rised the Pyton requestment for OpenOffic and it's not easy to upgrade the python on this machine. The other build machin is not seted up to build against 10.4. But I want to have a actual build from truck for automated tests. Can someone offer such builds to me. can you try again and update configure.in first (update, autoconf, ...) I hope it works now for you using the system Python. And please let me know if it works Juergen The Windows and Linux builds I can take from the buildbot. Greetings Raphael - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Proposal
Good morning, I am Juan Carlos de Val, a Mechanical Engineering student who has an idea and wants to begin being a entrepreneur. My question was about your legacy, because I don´t know if I would be able to use your software to offer it (obviously 100% for free) but on a new platform. Thank you very much. Juan Carlos de Val Telf.: Spain +34 619 67 59 82 Italy: +39 388 956 0099 juancarlos.de...@gmail.com
Re: buildbots -- Linux and MacOSX
School for the week is over. Let me just configure this SVN repo thing (I use Git, sorry) and the whole environment. A couple of questions - Am I right to presume that I need the 4 GB trunk to start building? - What set of details do you guys need from me? On Thu, Nov 14, 2013 at 2:01 AM, Kay Schenk kay.sch...@gmail.com wrote: On Tue, Nov 12, 2013 at 6:33 PM, Glenn Harvey Liwanag glennharveyliwa...@gmail.com wrote: I can try building the thing on my Mac OS X if that's what you're looking for. It's my only computer right now and I use it for school so I have to know first the average build time and the instructions to get the whole thing done without academics interfering with the work. Thanks for this offer! Resources used for building are dependent on your system, but typically it would take about 2 hours for a full build. Information on how to obtain the source and a link to the Building Guide can be found on the project source page: http://openoffice.apache.org/source.html Please let us know how this goes for you. On Wed, Nov 13, 2013 at 9:08 AM, Kay Schenk kay.sch...@gmail.com wrote: Regarding Jürgen's comments on a recent thread -- http://markmail.org/message/v5zli2np67qv5ryz Since CentOS 5 is our reference distribution for delivered Linux binaries (I did not know this!) -- and I am assuming this distro might remain as the reference going forward, does it make sense to try to move forward to set this up as a buildbot. I know wokr had already started on this. Can someone give us an update? https://issues.apache.org/jira/browse/INFRA-6217 I don't know CentOS, but having about 18 years in various *nixes HP/UX, Solaris, RedHat, SuSE), I could probably help assuming I could work in command line only to deal with this. On the MacOSX front, the latest update indicates we don't have hardware :( https://issues.apache.org/jira/browse/INFRA-4902 Any suggestions? Volunteers with equipment to dedicate to this? -- - MzK “Unless someone like you cares a whole awful lot, Nothing is going to get better. It's not.” -- Dr. Seuss, The Lorax -- - MzK “Unless someone like you cares a whole awful lot, Nothing is going to get better. It's not.” -- Dr. Seuss, The Lorax
[code] build breaker on Linux 64bit in introduced ia2 code
Hi Steve, can you please have look at the build breaker on Linux 64bit, found by our corresponding Linux 64bit build bot. The build breaks in module accessibility. The relevante build output is: build output ... Compiling: accessibility/source/standard/vclxaccessiblelist.cxx ... /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx: In member function 'virtual void VCLXAccessibleList::ProcessWindowEvent(const VclWindowEvent, bool)': /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx:372: error: cast from 'void*' to 'sal_uInt32' loses precision /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx: At global scope: /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx:606: warning: unused parameter 'bItemInserted' /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx:606: warning: unused parameter 'nIndex' dmake: Error code 1, while making '../../unxlngx6.pro/slo/vclxaccessiblelist.obj' /build output Until the next Linux 64bit build bot is started, the complete build output can be found at [1]. [1] http://ci.apache.org/projects/openoffice/buildlogs/linux64/main/accessibility/unxlngx6.pro/misc/logs/source.standard.txt Thanks in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [code] build breaker on Linux 64bit in introduced ia2 code
Hi, kudos to Herbert. While I have written the below message Herbert has already provided the fix - see revision 1542228 Steve, may be you can have an additional look at the unused parameters. Best regards, Oliver. On 15.11.2013 12:09, Oliver-Rainer Wittmann wrote: Hi Steve, can you please have look at the build breaker on Linux 64bit, found by our corresponding Linux 64bit build bot. The build breaks in module accessibility. The relevante build output is: build output ... Compiling: accessibility/source/standard/vclxaccessiblelist.cxx ... /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx: In member function 'virtual void VCLXAccessibleList::ProcessWindowEvent(const VclWindowEvent, bool)': /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx:372: error: cast from 'void*' to 'sal_uInt32' loses precision /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx: At global scope: /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx:606: warning: unused parameter 'bItemInserted' /home/buildslave19/slave19/openofficeorg-nightly/build/main/accessibility/source/standard/vclxaccessiblelist.cxx:606: warning: unused parameter 'nIndex' dmake: Error code 1, while making '../../unxlngx6.pro/slo/vclxaccessiblelist.obj' /build output Until the next Linux 64bit build bot is started, the complete build output can be found at [1]. [1] http://ci.apache.org/projects/openoffice/buildlogs/linux64/main/accessibility/unxlngx6.pro/misc/logs/source.standard.txt Thanks in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Apache OpenOffice 4.1 to Bring Enhanced Accessibility Support
Our latest blog post: https://blogs.apache.org/OOo/entry/apache_openoffice_4_1_to This accessibility code has now been integrated into the trunk. This is a great step forward. If you refresh yourself on our posted Public Service Mission, you see that accessibility is a key priority for us: http://openoffice.apache.org/mission.html This code came from IBM's contribution of Lotus Symphony, but much effort was required to integrate it into OpenOffice. Our thanks go to Steve Yin for the development work and to V Stuart Foote, James Teh, Jean-Philippe Mengual and Liu Ping for their expertise on testing. (And profuse apologies if I missed anyone) Regards. -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: buildbots -- Linux and MacOSX
On Tue, Nov 12, 2013 at 9:33 PM, Glenn Harvey Liwanag glennharveyliwa...@gmail.com wrote: I can try building the thing on my Mac OS X if that's what you're looking for. It's my only computer right now and I use it for school so I have to know first the average build time and the instructions to get the whole thing done without academics interfering with the work. A buildbot is a server that does automated builds for us in a secure environment. So it is more complicated than a build environment set up on an developer's machine. That said, you are welcome to set up a build environment on your own machine if you are interested in helping with bug fixes or things like that. Regards, -Rob On Wed, Nov 13, 2013 at 9:08 AM, Kay Schenk kay.sch...@gmail.com wrote: Regarding Jürgen's comments on a recent thread -- http://markmail.org/message/v5zli2np67qv5ryz Since CentOS 5 is our reference distribution for delivered Linux binaries (I did not know this!) -- and I am assuming this distro might remain as the reference going forward, does it make sense to try to move forward to set this up as a buildbot. I know wokr had already started on this. Can someone give us an update? https://issues.apache.org/jira/browse/INFRA-6217 I don't know CentOS, but having about 18 years in various *nixes HP/UX, Solaris, RedHat, SuSE), I could probably help assuming I could work in command line only to deal with this. On the MacOSX front, the latest update indicates we don't have hardware :( https://issues.apache.org/jira/browse/INFRA-4902 Any suggestions? Volunteers with equipment to dedicate to this? -- - MzK “Unless someone like you cares a whole awful lot, Nothing is going to get better. It's not.” -- Dr. Seuss, The Lorax - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Proposal] Update 'Get It Here' Banner
Ok no one voted +1 nor -1 explicitly, but it sounds like people are happy with the new banner. On Sun, Nov 10, 2013 at 12:55 PM, Samer Mansour samer...@gmail.com wrote: Hey everyone, Just realized the 'get it here' image is out dated. So I whipped together a new banner with a design I've been using with our social media pages. This is the current banner: http://openoffice.apache.org/images/get-it-here/en.png (from http://openoffice.apache.org/get-it-here.html) This is what I'm proposing to replace: http://dynomie.com/ext/getithere2.png I would replace the current one with the same dimensions so that it updates nicely on other sites with the existing logo code (if they pointed to our hosted image). Lazy consensus as usual, 72 hours. Samer Mansour
Re: Apache OpenOffice 4.1 to Bring Enhanced Accessibility Support
Rob, Great news! Great blog post--subtle ;-) On a side bar, I see that Herbert and Oliver are hard at work correcting build issues for Steve's rev 1541847 integration done yesterday, getting the new IAccessible2 bridge to build cleanly on trunk is obviously now the priority. But when someone gets a chance there are several source files from the merge that will need to have ALv2 headers inserted--don't want the down stream folks to complain too loudly... Stuart Here is a working list of the ones I've reviewed, they've all still got the LGPLv3 headers: /aoo-trunk/main/editeng/inc/editeng/AccessibleSvxFindReplaceDialog.hxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/editeng/inc/editeng/AccessibleSvxFindReplaceDialog.hxx /aoo-trunk/main/offapi/com/sun/star/accessibility/MSAAService.idl http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/offapi/com/sun/star/accessibility/MSAAService.idl /aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleExtendedAttributes.idl http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleExtendedAttributes.idl /aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleGetAccFlowTo.idl http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleGetAccFlowTo.idl /aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleGroupPosition.idl http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleGroupPosition.idl /aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleTableSelection.idl http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleTableSelection.idl /aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleTextSelection.idl http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/offapi/com/sun/star/accessibility/XAccessibleTextSelection.idl /aoo-trunk/main/offapi/com/sun/star/accessibility/XMSAAService.idl http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/offapi/com/sun/star/accessibility/XMSAAService.idl /aoo-trunk/main/svtools/inc/svtools/accessibleruler.hxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svtools/inc/svtools/accessibleruler.hxx /aoo-trunk/main/svtools/inc/svtools/vclxaccessibleheaderbar.hxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svtools/inc/svtools/vclxaccessibleheaderbar.hxx /aoo-trunk/main/svtools/inc/svtools/vclxaccessibleheaderbaritem.hxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svtools/inc/svtools/vclxaccessibleheaderbaritem.hxx /aoo-trunk/main/svtools/source/control/accessibleruler.cxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svtools/source/control/accessibleruler.cxx /aoo-trunk/main/svtools/source/control/ruler.src http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svtools/source/control/ruler.src /aoo-trunk/main/svtools/source/control/vclxaccessibleheaderbar.cxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svtools/source/control/vclxaccessibleheaderbar.cxx /aoo-trunk/main/svtools/source/control/vclxaccessibleheaderbaritem.cxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svtools/source/control/vclxaccessibleheaderbaritem.cxx /aoo-trunk/main/svx/source/inc/svxpixelctlaccessiblecontext.hxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svx/source/inc/svxpixelctlaccessiblecontext.hxx /aoo-trunk/main/sw/source/core/access/accfield.cxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/sw/source/core/access/accfield.cxx /aoo-trunk/main/sw/source/core/access/accfield.hxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/sw/source/core/access/accfield.hxx /aoo-trunk/main/sw/source/core/access/accnotexthyperlink.cxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/sw/source/core/access/accnotexthyperlink.cxx /aoo-trunk/main/sw/source/core/access/accnotexthyperlink.hxx http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/sw/source/core/access/accnotexthyperlink.hxx -- View this message in context: http://openoffice.2283327.n4.nabble.com/Apache-OpenOffice-4-1-to-Bring-Enhanced-Accessibility-Support-tp4655818p4655825.html Sent from the Development mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build braker in rejuvenate01 cppu
Just a small status update to my mail from Tuesday: On 12.11.2013 10:17, Herbert Dürr wrote: On 11.11.2013 10:47, Raphael Bircher wrote: I run in a build breaker in the rejuvenate01 branche dmake: Error: -- `uno_purpenvhelpers5abi.map' not found, and can't be made I just committed r1540968 to add the missing file by renaming its older cousin. Has someone a idea what happend here, and what's wrong? [...] Thanks for looking into the rejuvenate01 branch. With the renaming and the recent major update from trunk it has become a construction site though. After the RmMoz work I can now focus on getting the branch round again and make it a viable port. So stay tuned, in a few days it will build+run out of the box again and it will have gained an important feature it missed so far: support for password protected documents! The rejuvenate01 branch should build out of the box again. Note the working support for password protected documents and the latest goodies we got by resyncing to trunk. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice 4.1 to Bring Enhanced Accessibility Support
On 15.11.2013 17:06, V Stuart Foote wrote: Rob, Great news! Great blog post--subtle ;-) On a side bar, I see that Herbert and Oliver are hard at work correcting build issues for Steve's rev 1541847 integration done yesterday, getting the new IAccessible2 bridge to build cleanly on trunk is obviously now the priority. But when someone gets a chance there are several source files from the merge that will need to have ALv2 headers inserted--don't want the down stream folks to complain too loudly... Good point, thanks for finding it! I fixed the license headers to the ALv2 as intended and moved the SNAPSHOT tag to the new revision. The next SNAPSHOT build is expected to be ready for downloading and testing next Monday evening. Have a great weekend and have fun with the next SNAPSHOT build! Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [code] solution for issue 33737 - in-place editing of Input Fields
Hi, On 13.11.2013 14:56, Oliver-Rainer Wittmann wrote: Hi, On 07.11.2013 18:21, Oliver-Rainer Wittmann wrote: Hi, I am working on a solution for issue 33737 [1] and I am making good progress. I have started the documentation of the solution in our wiki - please have a look at https://wiki.openoffice.org/wiki/Writer/Input_Fields. It should be almost complete - may be I have forgotten the one or the other which will follow when I get notice of its missing. If you are interested in this area, please have a look and provide feedback. Thanks in advance. [1] https://issues.apache.org/ooo/show_bug.cgi?id=33737 I have finished the implementation. Unfortunately, my test on MacOS X reveals some problems: - special characters inserted for improved cursor traveling are more or less visible - traveling from one Input Field to the other skips one Input Fields. This happens on forward and backward traveling. Thus, I back on the coding. I assume to solve the problems at least until the end of the week. I have solved the problem on MacOS X. I will check the final code changes on the major platforms (Windows, Linux and MacOS X). I expect that the code changes will be committed into trunk at the beginning of next week. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: buildbots -- Linux and MacOSX
I wanted to give an update on the buildbots, as this is a question that keeps coming up. * We've received assurances that the Mac buildbot is coming. Long story short, the current mac hardware is a bit long in the tooth and we would kill everything on it if we added our builds to the current machine. We are waiting for real hardware in the form of a Mac Pro which will enable us to have multiple virtualized mac bots, giving us our own environment that can be set up for AOO. The machine should be ordered by the end of the year - bot should come up early next year - ish... * We are also waiting on a CentOS bot to create our standard Linux build. This has been requested and is in the works, and Jan has agreed to bring this up in discussions with infra. I am hoping we can have this for the 4.1 release timeframe. * FreeBSD bot - we have a new freebsd bot and it is slowly moving toward building without errors. If anyone has suggestions for fixing issues on there, please post to dev and we'll move that forward. We are currently stuck on Hunspell - http://ci.apache.org/builders/openoffice-fbsd-nightly/builds/91/steps/configure/logs/stdio and http://ci.apache.org/projects/openoffice/buildlogs/fbsdn/log/unxfbsdx.pro.build.html * The hung process issue with the windows buildbots seems to solved now, and has not been a problem lately. * Currently the Windows bots are failing - but this seems to an issue of svn getting out of sync, I'm cleaning up the bot and restarting the machine after some updates - I expect this to clean up the current issues. ( * Snapshots - both linux and windoze are currently having issues in terms of the size of files that the build creates. The standard buildbot directory upload routine zips the directory, uploads it, and unzips at the destination. Our directory of install bits has gotten too large and we are running into an exception on this step. (On long term fix is to create our own custom directory upload code for build bot - but that is another discussion...) The short term solution is to split the snapshot build into two builds (possible in a single flow) and build half the languages in each build - this should get us around the space issue. That's all for now A. On 11/13/2013 10:01 AM, Kay Schenk wrote: On Tue, Nov 12, 2013 at 6:33 PM, Glenn Harvey Liwanag glennharveyliwa...@gmail.com wrote: I can try building the thing on my Mac OS X if that's what you're looking for. It's my only computer right now and I use it for school so I have to know first the average build time and the instructions to get the whole thing done without academics interfering with the work. Thanks for this offer! Resources used for building are dependent on your system, but typically it would take about 2 hours for a full build. Information on how to obtain the source and a link to the Building Guide can be found on the project source page: http://openoffice.apache.org/source.html Please let us know how this goes for you. On Wed, Nov 13, 2013 at 9:08 AM, Kay Schenk kay.sch...@gmail.com wrote: Regarding Jürgen's comments on a recent thread -- http://markmail.org/message/v5zli2np67qv5ryz Since CentOS 5 is our reference distribution for delivered Linux binaries (I did not know this!) -- and I am assuming this distro might remain as the reference going forward, does it make sense to try to move forward to set this up as a buildbot. I know wokr had already started on this. Can someone give us an update? https://issues.apache.org/jira/browse/INFRA-6217 I don't know CentOS, but having about 18 years in various *nixes HP/UX, Solaris, RedHat, SuSE), I could probably help assuming I could work in command line only to deal with this. On the MacOSX front, the latest update indicates we don't have hardware :( https://issues.apache.org/jira/browse/INFRA-4902 Any suggestions? Volunteers with equipment to dedicate to this? -- - MzK “Unless someone like you cares a whole awful lot, Nothing is going to get better. It's not.” -- Dr. Seuss, The Lorax
Re: [discuss] drop support for Java 5 and Java 6 for Windows
On Thu, Nov 14, 2013 at 11:53 PM, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 15.11.2013 08:38, janI wrote: On 15 November 2013 08:25, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 15.11.2013 00:54, Kay Schenk wrote: On Wed, Nov 13, 2013 at 11:26 PM, janI j...@apache.org wrote: On 14 November 2013 03:32, Kay Schenk kay.sch...@gmail.com wrote: On Sun, Sep 22, 2013 at 5:11 AM, Andrea Pescetti pesce...@apache.org wrote: On 12/09/2013 Kay Schenk wrote: Did we reach a consensus on this one? Wait until 4.1 to officially change java build environment to 7? Buildbots are still at 6, although I know some of us are using 7 for building with no problems. We didn't reach consensus, the reason being (rather than disagreement) that it's unclear: - what the proposal is about exactly - what's broken in the current setup - what's the impact on people who wish to build OpenOffice - what's the impact on people who wish to use OpenOffice Now, after yet another discussion where we explain Java to each other, we can take for granted that we all know about it and move on and see what the proposal is about in concrete, so that is can be evaluated properly and maybe implemented in time for 4.1. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org OK, I'm back on this old thread. The thing is the security considerations do not just apply to Windows. I suggest we switch to java 7 as default and change the settings for javacompiler in configure.in appropriately to deal with this. Although by default, I build with java 7, I will make this change locally and see what happens. +1, so we use java 7 for development, but the final installation still runs with both java 6 and java 7. rgds jan I. Well, in theory, yes. In practice -- I guess not. :( I changed my configure.in etc and rebuilt. Then a final stop with this message -- javac: source release 1.7 requires target release 1.7 in module jvmfwk The man page for javac (openJDK 7)has this info talks about default values for targets depending on source...here are the last bits of that o If -source is 1.5, the value of -target is 1.7 o If -source is 1.6, the value of -target is 1.7 o For all other values of -source, the value of -target is the value of -source. but no specific information saying iyou can NOT specify a target value that is below your source value. I imagine this is universal and not just specific to openJDK but I don't know for sure. Any other ideas? On my attempt to build on Windows with Java 1.7 (Windows 7 64bit Home Premium VM) I did the following: After having setup the build environment via configure, bootstrap and sourcing the creating 'winenv.set.sh' I set the environment variable JAVAFLAGS to -source 1.5 -target 1.5 by command - export JAVAFLAGS='-source 1.5 -target 1.5' My build was sucessfull and the resulting installation set worked on a different Windows machine with Java 1.6 I have done a similar thing on ubuntu 12.04, manually modified LinuxX86-64Env.Set.sh and it builds correctly. Unfortunately, I did not continued my work on it - e.g. - detecting the Java version during configure - setting JAVAFLAGS automatically depending on the detected Java version It seems the right place to do this is configure.in. But why detect version, why not simple set the flags ? Yes, you are right. When it works in the build environment with all the different Java versions this is the simply solution. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Unfortunately for this little trial, I apparently misunderstood the reasoning, and did this -- javac -source 1.7 -target 1.5 which javac got upset with, and thus my error. On the other hand, I did get a lot of warnings (I use verbose build option) -- not permanently kept -- that were no doubt about deprecated or changed methods in our current code. These may be useful to us, I don't know. Maybe we don't need the -source, just -target? I also changed some of the other java requirements in configure.in to require 1.7 for building. So, I will play with this more in the next few days, and report back. -- - MzK “Unless someone like you cares a whole awful lot, Nothing is going to get better. It's not.” -- Dr. Seuss, The Lorax
Re: buildbots -- Linux and MacOSX
[top posting] Thank you for this update! :) On Fri, Nov 15, 2013 at 9:54 AM, Andrew Rist andrew.r...@oracle.com wrote: I wanted to give an update on the buildbots, as this is a question that keeps coming up. * We've received assurances that the Mac buildbot is coming. Long story short, the current mac hardware is a bit long in the tooth and we would kill everything on it if we added our builds to the current machine. We are waiting for real hardware in the form of a Mac Pro which will enable us to have multiple virtualized mac bots, giving us our own environment that can be set up for AOO. The machine should be ordered by the end of the year - bot should come up early next year - ish... * We are also waiting on a CentOS bot to create our standard Linux build. This has been requested and is in the works, and Jan has agreed to bring this up in discussions with infra. I am hoping we can have this for the 4.1 release timeframe. * FreeBSD bot - we have a new freebsd bot and it is slowly moving toward building without errors. If anyone has suggestions for fixing issues on there, please post to dev and we'll move that forward. We are currently stuck on Hunspell - http://ci.apache.org/builders/openoffice-fbsd-nightly/ builds/91/steps/configure/logs/stdio and http://ci.apache.org/projects/openoffice/buildlogs/fbsdn/ log/unxfbsdx.pro.build.html * The hung process issue with the windows buildbots seems to solved now, and has not been a problem lately. * Currently the Windows bots are failing - but this seems to an issue of svn getting out of sync, I'm cleaning up the bot and restarting the machine after some updates - I expect this to clean up the current issues. ( * Snapshots - both linux and windoze are currently having issues in terms of the size of files that the build creates. The standard buildbot directory upload routine zips the directory, uploads it, and unzips at the destination. Our directory of install bits has gotten too large and we are running into an exception on this step. (On long term fix is to create our own custom directory upload code for build bot - but that is another discussion...) The short term solution is to split the snapshot build into two builds (possible in a single flow) and build half the languages in each build - this should get us around the space issue. That's all for now A. On 11/13/2013 10:01 AM, Kay Schenk wrote: On Tue, Nov 12, 2013 at 6:33 PM, Glenn Harvey Liwanag glennharveyliwa...@gmail.com wrote: I can try building the thing on my Mac OS X if that's what you're looking for. It's my only computer right now and I use it for school so I have to know first the average build time and the instructions to get the whole thing done without academics interfering with the work. Thanks for this offer! Resources used for building are dependent on your system, but typically it would take about 2 hours for a full build. Information on how to obtain the source and a link to the Building Guide can be found on the project source page: http://openoffice.apache.org/source.html Please let us know how this goes for you. On Wed, Nov 13, 2013 at 9:08 AM, Kay Schenk kay.sch...@gmail.com wrote: Regarding Jürgen's comments on a recent thread -- http://markmail.org/message/v5zli2np67qv5ryz Since CentOS 5 is our reference distribution for delivered Linux binaries (I did not know this!) -- and I am assuming this distro might remain as the reference going forward, does it make sense to try to move forward to set this up as a buildbot. I know wokr had already started on this. Can someone give us an update? https://issues.apache.org/jira/browse/INFRA-6217 I don't know CentOS, but having about 18 years in various *nixes HP/UX, Solaris, RedHat, SuSE), I could probably help assuming I could work in command line only to deal with this. On the MacOSX front, the latest update indicates we don't have hardware :( https://issues.apache.org/jira/browse/INFRA-4902 Any suggestions? Volunteers with equipment to dedicate to this? -- - MzK “Unless someone like you cares a whole awful lot, Nothing is going to get better. It's not.” -- Dr. Seuss, The Lorax -- - MzK “Unless someone like you cares a whole awful lot, Nothing is going to get better. It's not.” -- Dr. Seuss, The Lorax
Re: [discuss] drop support for Java 5 and Java 6 for Windows
On 15 November 2013 18:59, Kay Schenk kay.sch...@gmail.com wrote: On Thu, Nov 14, 2013 at 11:53 PM, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 15.11.2013 08:38, janI wrote: On 15 November 2013 08:25, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 15.11.2013 00:54, Kay Schenk wrote: On Wed, Nov 13, 2013 at 11:26 PM, janI j...@apache.org wrote: On 14 November 2013 03:32, Kay Schenk kay.sch...@gmail.com wrote: On Sun, Sep 22, 2013 at 5:11 AM, Andrea Pescetti pesce...@apache.org wrote: On 12/09/2013 Kay Schenk wrote: Did we reach a consensus on this one? Wait until 4.1 to officially change java build environment to 7? Buildbots are still at 6, although I know some of us are using 7 for building with no problems. We didn't reach consensus, the reason being (rather than disagreement) that it's unclear: - what the proposal is about exactly - what's broken in the current setup - what's the impact on people who wish to build OpenOffice - what's the impact on people who wish to use OpenOffice Now, after yet another discussion where we explain Java to each other, we can take for granted that we all know about it and move on and see what the proposal is about in concrete, so that is can be evaluated properly and maybe implemented in time for 4.1. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org OK, I'm back on this old thread. The thing is the security considerations do not just apply to Windows. I suggest we switch to java 7 as default and change the settings for javacompiler in configure.inappropriately to deal with this. Although by default, I build with java 7, I will make this change locally and see what happens. +1, so we use java 7 for development, but the final installation still runs with both java 6 and java 7. rgds jan I. Well, in theory, yes. In practice -- I guess not. :( I changed my configure.in etc and rebuilt. Then a final stop with this message -- javac: source release 1.7 requires target release 1.7 in module jvmfwk The man page for javac (openJDK 7)has this info talks about default values for targets depending on source...here are the last bits of that o If -source is 1.5, the value of -target is 1.7 o If -source is 1.6, the value of -target is 1.7 o For all other values of -source, the value of -target is the value of -source. but no specific information saying iyou can NOT specify a target value that is below your source value. I imagine this is universal and not just specific to openJDK but I don't know for sure. Any other ideas? On my attempt to build on Windows with Java 1.7 (Windows 7 64bit Home Premium VM) I did the following: After having setup the build environment via configure, bootstrap and sourcing the creating 'winenv.set.sh' I set the environment variable JAVAFLAGS to -source 1.5 -target 1.5 by command - export JAVAFLAGS='-source 1.5 -target 1.5' My build was sucessfull and the resulting installation set worked on a different Windows machine with Java 1.6 I have done a similar thing on ubuntu 12.04, manually modified LinuxX86-64Env.Set.sh and it builds correctly. Unfortunately, I did not continued my work on it - e.g. - detecting the Java version during configure - setting JAVAFLAGS automatically depending on the detected Java version It seems the right place to do this is configure.in. But why detect version, why not simple set the flags ? Yes, you are right. When it works in the build environment with all the different Java versions this is the simply solution. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Unfortunately for this little trial, I apparently misunderstood the reasoning, and did this -- javac -source 1.7 -target 1.5 which javac got upset with, and thus my error. On the other hand, I did get a lot of warnings (I use verbose build option) -- not permanently kept -- that were no doubt about deprecated or changed methods in our current code. These may be useful to us, I don't know. How about making a BZ with the deprecated or changed methods, that could be a nice task a java developer. Maybe we don't need the -source, just -target? On ubuntu, it assumed 1.7 if I did not specify -source, and that gave me a lot of warnings (could be the same you saw). Adding -source 1.5 tell java that the source is 1.5. I also
Reporting a problem with the OpenOffice website
Bonjour, Le 23.10.2013 à 19h09 j'ai téléchargé une version normalement gratuite d'open office sur votre site internet. Pour cela il fallait envoyer 2 sms pour obtenir des codes afin de poursuivre le téléchargement. Aujourd'hui ces 2 sms me sont facturés 10euros TTC par mon opérateur! Aussi la notion de gratuité n'est elle pas l’absence de transaction financière? Cordialement, Laurence Couvreur.
Re: Reporting a problem with the OpenOffice website
2013/11/15 couvreur laurence couvre...@yahoo.fr Bonjour, Le 23.10.2013 à 19h09 j'ai téléchargé une version normalement gratuite d'open office sur votre site internet. Pour cela il fallait envoyer 2 sms pour obtenir des codes afin de poursuivre le téléchargement. Aujourd'hui ces 2 sms me sont facturés 10euros TTC par mon opérateur! Aussi la notion de gratuité n'est elle pas l’absence de transaction financière? Cordialement, Laurence Couvreur. openoffice.org ?
Re: Reporting a problem with the OpenOffice website
Am 11/15/2013 07:29 PM, schrieb couvreur laurence: Bonjour, Le 23.10.2013 à 19h09 j'ai téléchargé une version normalement gratuite d'open office sur votre site internet. Pour cela il fallait envoyer 2 sms pour obtenir des codes afin de poursuivre le téléchargement. Aujourd'hui ces 2 sms me sont facturés 10euros TTC par mon opérateur! Aussi la notion de gratuité n'est elle pas l’absence de transaction financière? Cordialement, Laurence Couvreur. First of all, this is an English-speaking mailing list. I don't know any French, so please allow me to answer in English. You cannot have downloaded OpenOffice from our (www.openoffice.org) website as we don't charge any money to download our software. In general, please download only from the original vendor or at least from approved/trusted 3rd party websites. For Apache OpenOffice please use only the following download webpage. This will forward you to a download offering from our partner SourgeForge: http://www.openoffice.org/download/ HTH Marcus FYI - English translation from Google: On 23.10.2013 at 19h09 I downloaded a free version of normally open office on your website. For this it was necessary to send 2 sms to obtain codes to continue downloading. Today these two sms are charged me 10 euros TTC per my operator! Also the notion of free Is not the lack of financial transaction? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: buildbots -- Linux and MacOSX
Really promizing and great news. Thanks for the detailed update. Marcus Am 11/15/2013 06:54 PM, schrieb Andrew Rist: I wanted to give an update on the buildbots, as this is a question that keeps coming up. * We've received assurances that the Mac buildbot is coming. Long story short, the current mac hardware is a bit long in the tooth and we would kill everything on it if we added our builds to the current machine. We are waiting for real hardware in the form of a Mac Pro which will enable us to have multiple virtualized mac bots, giving us our own environment that can be set up for AOO. The machine should be ordered by the end of the year - bot should come up early next year - ish... * We are also waiting on a CentOS bot to create our standard Linux build. This has been requested and is in the works, and Jan has agreed to bring this up in discussions with infra. I am hoping we can have this for the 4.1 release timeframe. * FreeBSD bot - we have a new freebsd bot and it is slowly moving toward building without errors. If anyone has suggestions for fixing issues on there, please post to dev and we'll move that forward. We are currently stuck on Hunspell - http://ci.apache.org/builders/openoffice-fbsd-nightly/builds/91/steps/configure/logs/stdio and http://ci.apache.org/projects/openoffice/buildlogs/fbsdn/log/unxfbsdx.pro.build.html * The hung process issue with the windows buildbots seems to solved now, and has not been a problem lately. * Currently the Windows bots are failing - but this seems to an issue of svn getting out of sync, I'm cleaning up the bot and restarting the machine after some updates - I expect this to clean up the current issues. ( * Snapshots - both linux and windoze are currently having issues in terms of the size of files that the build creates. The standard buildbot directory upload routine zips the directory, uploads it, and unzips at the destination. Our directory of install bits has gotten too large and we are running into an exception on this step. (On long term fix is to create our own custom directory upload code for build bot - but that is another discussion...) The short term solution is to split the snapshot build into two builds (possible in a single flow) and build half the languages in each build - this should get us around the space issue. That's all for now A. On 11/13/2013 10:01 AM, Kay Schenk wrote: On Tue, Nov 12, 2013 at 6:33 PM, Glenn Harvey Liwanag glennharveyliwa...@gmail.com wrote: I can try building the thing on my Mac OS X if that's what you're looking for. It's my only computer right now and I use it for school so I have to know first the average build time and the instructions to get the whole thing done without academics interfering with the work. Thanks for this offer! Resources used for building are dependent on your system, but typically it would take about 2 hours for a full build. Information on how to obtain the source and a link to the Building Guide can be found on the project source page: http://openoffice.apache.org/source.html Please let us know how this goes for you. On Wed, Nov 13, 2013 at 9:08 AM, Kay Schenk kay.sch...@gmail.com wrote: Regarding Jürgen's comments on a recent thread -- http://markmail.org/message/v5zli2np67qv5ryz Since CentOS 5 is our reference distribution for delivered Linux binaries (I did not know this!) -- and I am assuming this distro might remain as the reference going forward, does it make sense to try to move forward to set this up as a buildbot. I know wokr had already started on this. Can someone give us an update? https://issues.apache.org/jira/browse/INFRA-6217 I don't know CentOS, but having about 18 years in various *nixes HP/UX, Solaris, RedHat, SuSE), I could probably help assuming I could work in command line only to deal with this. On the MacOSX front, the latest update indicates we don't have hardware :( https://issues.apache.org/jira/browse/INFRA-4902 Any suggestions? Volunteers with equipment to dedicate to this? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Proposal] Update 'Get It Here' Banner
On 15/11/2013 Samer Mansour wrote: Ok no one voted +1 nor -1 explicitly, but it sounds like people are happy with the new banner. ... http://dynomie.com/ext/getithere2.png Sure, it was lazy consensus on my side. Nice job! Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Proposal] Update 'Get It Here' Banner
Am 11/15/2013 08:26 PM, schrieb Andrea Pescetti: On 15/11/2013 Samer Mansour wrote: Ok no one voted +1 nor -1 explicitly, but it sounds like people are happy with the new banner. ... http://dynomie.com/ext/getithere2.png FYI Only when we do an offical vote for something then +1 or -1 or 0 is important and counted - e.g., for a new AOO release. Otherwise it's just lazy consensus. Of course many of us write +1 to express that they like it. But this has no real meaning. It would also work without this as only the written text is taken into account. Sure, it was lazy consensus on my side. Nice job! Me too. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: buildbots -- Linux and MacOSX
Andrew Rist wrote: * We've received assurances that the Mac buildbot is coming. ... We are waiting for real hardware in the form of a Mac Pro which will enable us to have multiple virtualized mac bots, giving us our own environment that can be set up for AOO. The machine should be ordered by the end of the year - bot should come up early next year - ish... Thanks for the update. It's great to know that the Mac buildbot is coming, and many thanks should go to Infra for finding the time to deal with this. Looking forward to see it available. * We are also waiting on a CentOS bot to create our standard Linux build. This has been requested and is in the works, and Jan has agreed to bring this up in discussions with infra. I am hoping we can have this for the 4.1 release timeframe. If I remember the old conversations correctly, here we already had the hardware, and a very powerful one, and the next step was to provide a CentOS 5 virtual machine. Is that correct? Building a VM is not rocket science, and I think several of us would be able to help with this if this can help move forward. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Reporting a problem with the OpenOffice website
On Fri, Nov 15, 2013 at 2:00 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 11/15/2013 07:29 PM, schrieb couvreur laurence: Bonjour, Le 23.10.2013 à 19h09 j'ai téléchargé une version normalement gratuite d'open office sur votre site internet. Pour cela il fallait envoyer 2 sms pour obtenir des codes afin de poursuivre le téléchargement. Aujourd'hui ces 2 sms me sont facturés 10euros TTC par mon opérateur! Aussi la notion de gratuité n'est elle pas l’absence de transaction financière? Cordialement, Laurence Couvreur. First of all, this is an English-speaking mailing list. I don't know any French, so please allow me to answer in English. You cannot have downloaded OpenOffice from our (www.openoffice.org) website as we don't charge any money to download our software. In general, please download only from the original vendor or at least from approved/trusted 3rd party websites. For Apache OpenOffice please use only the following download webpage. This will forward you to a download offering from our partner SourgeForge: http://www.openoffice.org/download/ HTH Marcus FYI - English translation from Google: On 23.10.2013 at 19h09 I downloaded a free version of normally open office on your website. For this it was necessary to send 2 sms to obtain codes to continue downloading. Today these two sms are charged me 10 euros TTC per my operator! Also the notion of free Is not the lack of financial transaction? Assuming the translation worked properly, he's not saying he was charged money for the download. He's saying whatever site he was downloading from required him to send two text messages in order to get a validation code for the download. Then whoever he sent the texts to billed his phone. I'm guessing whatever site he used not only misrepresented AOO, it also misrepresented free and ripped him off. I find it ironic that there are two ads in my Gmail session as I type this offering Free OpenOffice Download. Don
Re: buildbots -- Linux and MacOSX
On 15 November 2013 20:52, Andrea Pescetti pesce...@apache.org wrote: Andrew Rist wrote: * We've received assurances that the Mac buildbot is coming. ... We are waiting for real hardware in the form of a Mac Pro which will enable us to have multiple virtualized mac bots, giving us our own environment that can be set up for AOO. The machine should be ordered by the end of the year - bot should come up early next year - ish... Thanks for the update. It's great to know that the Mac buildbot is coming, and many thanks should go to Infra for finding the time to deal with this. Looking forward to see it available. * We are also waiting on a CentOS bot to create our standard Linux build. This has been requested and is in the works, and Jan has agreed to bring this up in discussions with infra. I am hoping we can have this for the 4.1 release timeframe. If I remember the old conversations correctly, here we already had the hardware, and a very powerful one, and the next step was to provide a CentOS 5 virtual machine. Is that correct? Building a VM is not rocket science, and I think several of us would be able to help with this if this can help move forward. Discussions have been whether or not it should be a vm (that was my original suggestion) with ubuntu as base or if tethys should run centOS directly (that was a general AOO suggestion). This discussion drifted out in nothing, mostly because nobody made a decision and started to work the issue 6217 is also not really clear in this respect. It is for sure not rocket science to start a vm. The science part comes when starting to get the standard infra utilities and e.g. ldap to work. But all in all its just work, that needs to be done. I have it on the agenda for next weeks infra meeting, and I suspect we (infra) will decide how to do it and who in infra (you get 2 guesses) will take the lead. But of course if anybody else wants to do it, then I am sure that it can be arranged (just wondering, why it did not happen earlier). rgds jan I. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discuss] drop support for Java 5 and Java 6 for Windows
On Nov 15, 2013 10:34 AM, janI j...@apache.org wrote: On 15 November 2013 18:59, Kay Schenk kay.sch...@gmail.com wrote: On Thu, Nov 14, 2013 at 11:53 PM, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 15.11.2013 08:38, janI wrote: On 15 November 2013 08:25, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 15.11.2013 00:54, Kay Schenk wrote: On Wed, Nov 13, 2013 at 11:26 PM, janI j...@apache.org wrote: On 14 November 2013 03:32, Kay Schenk kay.sch...@gmail.com wrote: On Sun, Sep 22, 2013 at 5:11 AM, Andrea Pescetti pesce...@apache.org wrote: On 12/09/2013 Kay Schenk wrote: Did we reach a consensus on this one? Wait until 4.1 to officially change java build environment to 7? Buildbots are still at 6, although I know some of us are using 7 for building with no problems. We didn't reach consensus, the reason being (rather than disagreement) that it's unclear: - what the proposal is about exactly - what's broken in the current setup - what's the impact on people who wish to build OpenOffice - what's the impact on people who wish to use OpenOffice Now, after yet another discussion where we explain Java to each other, we can take for granted that we all know about it and move on and see what the proposal is about in concrete, so that is can be evaluated properly and maybe implemented in time for 4.1. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org OK, I'm back on this old thread. The thing is the security considerations do not just apply to Windows. I suggest we switch to java 7 as default and change the settings for javacompiler in configure.inappropriately to deal with this. Although by default, I build with java 7, I will make this change locally and see what happens. +1, so we use java 7 for development, but the final installation still runs with both java 6 and java 7. rgds jan I. Well, in theory, yes. In practice -- I guess not. :( I changed my configure.in etc and rebuilt. Then a final stop with this message -- javac: source release 1.7 requires target release 1.7 in module jvmfwk The man page for javac (openJDK 7)has this info talks about default values for targets depending on source...here are the last bits of that o If -source is 1.5, the value of -target is 1.7 o If -source is 1.6, the value of -target is 1.7 o For all other values of -source, the value of -target is the value of -source. but no specific information saying iyou can NOT specify a target value that is below your source value. I imagine this is universal and not just specific to openJDK but I don't know for sure. Any other ideas? On my attempt to build on Windows with Java 1.7 (Windows 7 64bit Home Premium VM) I did the following: After having setup the build environment via configure, bootstrap and sourcing the creating 'winenv.set.sh' I set the environment variable JAVAFLAGS to -source 1.5 -target 1.5 by command - export JAVAFLAGS='-source 1.5 -target 1.5' My build was sucessfull and the resulting installation set worked on a different Windows machine with Java 1.6 I have done a similar thing on ubuntu 12.04, manually modified LinuxX86-64Env.Set.sh and it builds correctly. Unfortunately, I did not continued my work on it - e.g. - detecting the Java version during configure - setting JAVAFLAGS automatically depending on the detected Java version It seems the right place to do this is configure.in. But why detect version, why not simple set the flags ? Yes, you are right. When it works in the build environment with all the different Java versions this is the simply solution. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Unfortunately for this little trial, I apparently misunderstood the reasoning, and did this -- javac -source 1.7 -target 1.5 which javac got upset with, and thus my error. On the other hand, I did get a lot of warnings (I use verbose build option) -- not permanently kept -- that were no doubt about deprecated or changed methods in our current code. These may be useful to us, I don't know. How about making a BZ with the deprecated or changed methods, that could be a nice task a
Re: Build braker in rejuvenate01 cppu
Hi Herbert Am 15.11.13 17:17, schrieb Herbert Duerr: Just a small status update to my mail from Tuesday: On 12.11.2013 10:17, Herbert Dürr wrote: On 11.11.2013 10:47, Raphael Bircher wrote: I run in a build breaker in the rejuvenate01 branche dmake: Error: -- `uno_purpenvhelpers5abi.map' not found, and can't be made I just committed r1540968 to add the missing file by renaming its older cousin. Has someone a idea what happend here, and what's wrong? [...] Thanks for looking into the rejuvenate01 branch. With the renaming and the recent major update from trunk it has become a construction site though. After the RmMoz work I can now focus on getting the branch round again and make it a viable port. So stay tuned, in a few days it will build+run out of the box again and it will have gained an important feature it missed so far: support for password protected documents! The rejuvenate01 branch should build out of the box again. Note the working support for password protected documents and the latest goodies we got by resyncing to trunk. No, at me it does not working it stops at testtools as far I can see. COPY: ../config/Linguistic-lingucomponent-thesaurus.xcu - /Users/nacnaub/Documents/rejuvenate01/main/solver/410/unxmaccx.pro/xml/registry/data/org/openoffice/Office/Linguistic-lingucomponent-thesaurus.xcu COPY: ../unxmaccx.pro/misc/MacOSXSpell.component - /Users/nacnaub/Documents/rejuvenate01/main/solver/410/unxmaccx.pro/xml/MacOSXSpell.component COPY: ../unxmaccx.pro/misc/guesslang.component - /Users/nacnaub/Documents/rejuvenate01/main/solver/410/unxmaccx.pro/xml/guesslang.component COPY: ../unxmaccx.pro/misc/hyphen.component - /Users/nacnaub/Documents/rejuvenate01/main/solver/410/unxmaccx.pro/xml/hyphen.component COPY: ../unxmaccx.pro/misc/lnth.component - /Users/nacnaub/Documents/rejuvenate01/main/solver/410/unxmaccx.pro/xml/lnth.component COPY: ../unxmaccx.pro/misc/spell.component - /Users/nacnaub/Documents/rejuvenate01/main/solver/410/unxmaccx.pro/xml/spell.component LOG: writing /Users/nacnaub/Documents/rejuvenate01/main/solver/410/unxmaccx.pro/inc/lingucomponent/deliver.log Module 'lingucomponent' delivered successfully. 15 files copied, 10 files unchanged 3 module(s): epm testtools vcl need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /Users/nacnaub/Documents/rejuvenate01/main/testtools/source/bridgetest ERROR: error 65280 occurred while making /Users/nacnaub/Documents/rejuvenate01/main/vcl/prj ERROR: error 65280 occurred while making /Users/nacnaub/Documents/rejuvenate01/main/epm When you have fixed the errors in that module you can resume the build by running: build --from epm testtools vcl Greetings Raphael - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [code] build breaker on Linux 64bit in introduced ia2 code
Hi Oliver and Herbert, Sorry for the break. Thank you all for fixing it so quickly! On Fri, Nov 15, 2013 at 7:13 PM, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, kudos to Herbert. While I have written the below message Herbert has already provided the fix - see revision 1542228 Steve, may be you can have an additional look at the unused parameters. Best regards, Oliver. On 15.11.2013 12:09, Oliver-Rainer Wittmann wrote: Hi Steve, can you please have look at the build breaker on Linux 64bit, found by our corresponding Linux 64bit build bot. The build breaks in module accessibility. The relevante build output is: build output ... Compiling: accessibility/source/standard/vclxaccessiblelist.cxx ... /home/buildslave19/slave19/openofficeorg-nightly/build/ main/accessibility/source/standard/vclxaccessiblelist.cxx: In member function 'virtual void VCLXAccessibleList::ProcessWindowEvent(const VclWindowEvent, bool)': /home/buildslave19/slave19/openofficeorg-nightly/build/ main/accessibility/source/standard/vclxaccessiblelist.cxx:372: error: cast from 'void*' to 'sal_uInt32' loses precision /home/buildslave19/slave19/openofficeorg-nightly/build/ main/accessibility/source/standard/vclxaccessiblelist.cxx: At global scope: /home/buildslave19/slave19/openofficeorg-nightly/build/ main/accessibility/source/standard/vclxaccessiblelist.cxx:606: warning: unused parameter 'bItemInserted' /home/buildslave19/slave19/openofficeorg-nightly/build/ main/accessibility/source/standard/vclxaccessiblelist.cxx:606: warning: unused parameter 'nIndex' dmake: Error code 1, while making '../../unxlngx6.pro/slo/vclxaccessiblelist.obj' /build output Until the next Linux 64bit build bot is started, the complete build output can be found at [1]. [1] http://ci.apache.org/projects/openoffice/buildlogs/linux64/ main/accessibility/unxlngx6.pro/misc/logs/source.standard.txt Thanks in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Best Regards, Steve Yin
