Re: LeRoy K Newby Gallery
On 2016-12-28, 3:46 PM K. Newby Gallery wrote concerning "LeRoy K Newby Gallery": To Whom It May Concern; We can not access Open Office Files we repeatedly receive this dialoge box.. would someone please respond and tell me what to do? __ You need to delete the folder "org.openoffice.script.savedState". It is in the "Saved Application State" folder in your User/Library. See this post on the user forum for detailed instructions: https://forum.openoffice.org/en/forum/viewtopic.php?f=17=55755#p244931 Known bug listed in the release notes, with solution for the problem. https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0.1+Release+Notes#AOO4.0.1ReleaseNotes-KnownIssues -- As a courtesy I have sent a copy of this reply to you as well as to the mailing list. Do Not reply to me personally but just to the list at- replies to my personal email address will be ignored. Since you are not subscribed to this list you may not see all the replies to your query.To subscribe Apache OpenOffice mailing lists go to http://openoffice.apache.org/mailing-lists.html For user support you can also use The OpenOffice.org Community Forum http://user.services.openoffice.org/en/forum/ _ Larry I. Gusaas Moose Jaw, Saskatchewan Canada Website: http://larry-gusaas.com "An artist is never ahead of his time but most people are far behind theirs." - Edgard Varese
LeRoy K Newby Gallery
To Whom It May Concern; We can not access Open Office Files we repeatedly receive this dialoge box.. would someone please respond and tell me what to do?
Re: problems building trunk with options: --enable-pch // --enable-win-x64-shellext
Hi Oliver, I have to look twice, as I read your name. Do you get homesick? For all newer one. Oliver Brinzing was a engeneer at the SUN StarOffice/OpenOffice team. Am 12/28/2016 um 5:34 PM schrieb Oliver Brinzing: i started with aoo414 branch debug build and it worked. then i tried to build from trunk, but failed, until i disabled "--enable-pch". but build always stopped in module "extensions", source/activex/main, already reported: windows build breaks in module extensions - activex https://bz.apache.org/ooo/show_bug.cgi?id=126996 i removed "--enable-win-x64-shellext", and build finished successful. "enable-win-x64-shellext" seems to set BUILD_X64="TRUE". i noticed, our win buildbots do not use "enable-win-x64-shellext" too. my configuration: ./configure \ --with-dmake-url="http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2; \ --with-ant-home="/cygdrive/c/build/ant" \ --with-mozilla-build="/cygdrive/c/build/mozilla-build" \ --with-frame-home="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0" \ --with-psdk-home="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0" \ --with-midl-path="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0/bin" \ --with-cl-home="/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 9.0/VC" \ --with-mspdb-path="/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 9.0/Common7/IDE" \ --with-asm-home="/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin" \ --with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \ --with-jdk-home="/cygdrive/c/Program Files (x86)/Java/jdk1.7.0" \ --with-nsis-path="/cygdrive/c/Program Files (x86)/NSIS" \ --with-directx-home="/cygdrive/c/Program Files (x86)/Microsoft DirectX SDK (June 2010)" \ --with-atl-include-dir="/cygdrive/c/WinDDK/7600.16385.1/inc/atl71" \ --with-atl-lib-dir="/cygdrive/c/WinDDK/7600.16385.1/lib/ATL/i386" \ --with-mfc-include-dir="/cygdrive/c/WinDDK/7600.16385.1/inc/mfc42" \ --with-mfc-lib-dir="/cygdrive/c/WinDDK/7600.16385.1/lib/Mfc/i386" \ --with-package-format="installed msi" \ --enable-category-b \ --enable-bundled-dictionaries \ --with-lang="de" \ --without-stlport \ --without-junit \ --enable-verbose \ --disable-odk \ --without-fonts \ --disable-online-update \ --disable-strip-solver \ --enable-symbols \ --enable-dbgutil \ --enable-crashdump \ --enable-debug I'm a bit shocked, about the big list of configuration it needs to build from Windows. Have a nice day Raphael - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
problems building trunk with options: --enable-pch // --enable-win-x64-shellext
i started with aoo414 branch debug build and it worked. then i tried to build from trunk, but failed, until i disabled "--enable-pch". but build always stopped in module "extensions", source/activex/main, already reported: windows build breaks in module extensions - activex https://bz.apache.org/ooo/show_bug.cgi?id=126996 i removed "--enable-win-x64-shellext", and build finished successful. "enable-win-x64-shellext" seems to set BUILD_X64="TRUE". i noticed, our win buildbots do not use "enable-win-x64-shellext" too. my configuration: ./configure \ --with-dmake-url="http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2; \ --with-ant-home="/cygdrive/c/build/ant" \ --with-mozilla-build="/cygdrive/c/build/mozilla-build" \ --with-frame-home="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0" \ --with-psdk-home="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0" \ --with-midl-path="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0/bin" \ --with-cl-home="/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 9.0/VC" \ --with-mspdb-path="/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 9.0/Common7/IDE" \ --with-asm-home="/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin" \ --with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \ --with-jdk-home="/cygdrive/c/Program Files (x86)/Java/jdk1.7.0" \ --with-nsis-path="/cygdrive/c/Program Files (x86)/NSIS" \ --with-directx-home="/cygdrive/c/Program Files (x86)/Microsoft DirectX SDK (June 2010)" \ --with-atl-include-dir="/cygdrive/c/WinDDK/7600.16385.1/inc/atl71" \ --with-atl-lib-dir="/cygdrive/c/WinDDK/7600.16385.1/lib/ATL/i386" \ --with-mfc-include-dir="/cygdrive/c/WinDDK/7600.16385.1/inc/mfc42" \ --with-mfc-lib-dir="/cygdrive/c/WinDDK/7600.16385.1/lib/Mfc/i386" \ --with-package-format="installed msi" \ --enable-category-b \ --enable-bundled-dictionaries \ --with-lang="de" \ --without-stlport \ --without-junit \ --enable-verbose \ --disable-odk \ --without-fonts \ --disable-online-update \ --disable-strip-solver \ --enable-symbols \ --enable-dbgutil \ --enable-crashdump \ --enable-debug - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Buildbots are working again
Thanks a lot Damjan. Sounds really great. I will update my repository and try to build open office again. Maybe it works for me. :) All the best Peter Damjan Jovanovicschrieb am Mo., 26. Dez. 2016, 19:46: > Hi > > All the buildbots are successfully building now. > > The FreeBSD bot was fixed by changing the buildbot script to use Clang > instead of GCC. From what I've seen, on FreeBSD, loading a mixture of C++ > libraries built with GCC and C++ libraries built with Clang into the same > process, and using more advanced C++ features like exception handling, > causes memory corruption and crashes due to incompatible C++ ABIs; either > every library has to be built with GCC or every library has to be built > with Clang. In practice, the former requires a rebuild of the entire base > system and building all ports from source, which is why the latter is > better. > > The Linux bots were much harder to fix. The build was breaking because libc > isn't linked to in some gbuild modules, something that was fixed by > explicitly always linking to libc on Linux, and because Google Test wasn't > linking to libpthread, somehow resulting in missing symbols in at least > main/binaryurp when built without --enable-dbgutil, which was fixed by > explicitly linking it to libpthread. I don't like these linker mysteries, > which never happen on FreeBSD, and some of which can be worked around with > the "gold" linker... > > Damjan > -- Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu verhandeln.
Re: #DIV/0!
Often in regular business context a div/0 is defined to 0 because 0 is defined also as I do not know. Mathematically div/0 is defined as an enormous huge number of unknown size. In electronic signal theory, there is also a div/0 which is defined as ideal impulse with unlimited high. You see there the correct definition depends on its interpretation of the topic you use it. The correct way for resolving your issue if you know what the right definition is, should be the use of a if-claus. If (divisor = 0;;) I think you could use. Maybe I got the syntax wrong. Marcusschrieb am Di., 27. Dez. 2016, 11:09: > Am 12/24/2016 06:00 AM, schrieb Robert Marshall: > > I was offering a solution. > > > > The problem being when summing a series if any member is #DIV/0! > > > > The result is #DIV/0!. > > > > A simple solution is to sum the series in an available adjacent column. > > the only solution is to resolve the #DIV/0! situation. Check the root > cause, fix it and then you have a correct summation. Everything else > won't be the right way. > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu verhandeln.