Re: [RELEASE] Contents of OpenOffice 4.1.2
On 13 July 2015 at 10:19, Gavin McDonald ga...@16degrees.com.au wrote: With regards to digital signing, we have ‘test’ credits that can be used to practice on. I understood earlier on David, that the credits infra bought last year would expire this august and he was in doubt how much he would buy going forward. Do you have more recent information ? rgds jan i. Gav… On 13 Jul 2015, at 9:04 am, jan i j...@apache.org wrote: Hi I agree to use this as the overall plan, which of course needs to detailed. I do have a comment about digital signing. It is correct than I do not have spare cycles before mid october. Digital signing means in reality white listing the content, which are both our exe as well as many third part DLLs (some of the libraries are statically linked and not exposed outside the exe). Most of our third party libraries are pretty old (but works well for our purpose), and some of them have known security isses (not in the parts AOO uses). We need to upgrade the libraries that uses a DLL, otherwise we might whitelist a DLL with known security issues. This process is something we should do ahead of every release, and is not as such part of the digital signing, but digital signing makes it much more important. rgds jan I. On Sunday, July 12, 2015, Marcus marcus.m...@wtnet.de wrote: Am 07/12/2015 03:57 PM, schrieb Andrea Pescetti: It's time to decide what goes into 4.1.2 and what doesn't. Not in terms of specific bugfixes (we have the standard process of nominating release blockers for this and I don't plan to change it), but in terms of categories. The following is a realistic list of what we can have in 4.1.2. Shall we take it as the overall plan for 4.1.2? In general I see it the same way. Some comments inline. 2. Features * Windows 10: Millions of our users will run Windows 10 within a few weeks. OpenOffice is reported to work smoothly on Windows 10 pre-releases. Should any major Windows 10 incompatibilities appear, they should be fixed in 4.1.2. When we want to react on specific bug reports (we should do this in any case as Windows is still the most favorite platform) then we create automatically a release schedule of a few weeks after that date - which is for me late summer. Just to be sure we understand the same. BTW: Release date of Win10 is July, 29th. 3. Localization * Existing translations: Pootle is now tracking the 4.2.0 release, so translators do not have an immediate way to fix translations for 4.1.2. There is a possibility to check whether we can reuse the 4.2.0 strings for 4.1.2, but due to the version clash I would prefer to fix strings upon request, in the SDF files directly and only in the case of major, well-defined bugs (example: the Italian version has a typo in a main menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file manually to fix it for the 4.1.x line). This has also the advantage (when we don't get too many change requests) that we know in detail what is changing. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Sent from My iPad, sorry for any misspellings. Gav... (( ( ( )\ ) )\ ) )\ ) ( ) ) )\(()/((()/( (()/( )\ ) ( ) ( /( ( ( ( /( ( ( ( _)( /(_))/(_)) /(_)) ( (()/( )( ( /( ( )\()))())\ ( )\()) ))\ )())\ )\ _ )\ (_)) (_))_| (_)) )\ ) /(_))(()\ )(_)) )\ (_))/(()\ /((_) )\ (_))/ /((_)(()\ /((_) (_)_\(_)/ __|| |_ |_ _| _(_/((_) _| ((_)((_)_ ((_)| |_ ((_)(_))( ((_)| |_ (_))( ((_)(_)) / _ \ \__ \| __| | | | ' \))| _|| '_|/ _` |(_-| _|| '_|| || |/ _| | _|| || || '_|/ -_) /_/ \_\ |___/|_||___||_||_| |_| |_| \__,_|/__/ \__||_| \_,_|\__| \__| \_,_||_| \___|
Re: Are the Buildbots down?
On 13 Jul, Pedro Giffuni wrote: I did notice the buildbot was failing on nss(?). That's what I get for taking hunks from elsewhere :-P. Patch below ... As you might have noticed I don't spend much quality time with AOO lately :-(. I've been spending too much B-( Index: main/nss/makefile.mk === --- main/nss/makefile.mk(revision 1690824) +++ main/nss/makefile.mk(working copy) @@ -50,6 +50,10 @@ PATCH_FILES+=nss_macosx.patch .ENDIF # $(OS)==MACOSX +.IF $(OS)==FREEBSD +PATCH_FILES+=nss_freebsd.patch +.ENDIF + .IF $(debug) != .ELSE BUILD_OPT=1 Index: main/nss/nss_freebsd.patch === --- main/nss/nss_freebsd.patch (revision 0) +++ main/nss/nss_freebsd.patch (working copy) @@ -0,0 +1,14 @@ +--- misc/nss-3.14.4/mozilla/security/coreconf/FreeBSD.mk 2012-05-03 09:42:51.0 + misc/build/nss-3.14.4/mozilla/security/coreconf/FreeBSD.mk 2015-07-13 23:42:44.915864000 + +@@ -5,9 +5,8 @@ + + include $(CORE_DEPTH)/coreconf/UNIX.mk + +-DEFAULT_COMPILER = gcc +-CC= gcc +-CCC = g++ ++DEFAULT_COMPILER = $(CC) ++CCC = $(CXX) + RANLIB= ranlib + + CPU_ARCH = $(OS_TEST) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Are the Buildbots down?
On 13 Jul, Pedro Giffuni wrote: I did notice the buildbot was failing on nss(?). That's what I get for taking hunks from elsewhere :-P. Working on a patch for that ... - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Are the Buildbots down?
On 07/13/15 20:06, Don Lewis wrote: On 13 Jul, Pedro Giffuni wrote: On 07/13/15 11:29, Don Lewis wrote: ... OpenOffice has a clang patch that was not catching this. I hacked it for FreeBSD now: http://svn.apache.org/viewvc?view=revisionrevision=1690740 But there is certainly something wrong as clang is not being detected. I think clang defines __GNUC__, so with the existing clang patch we were still using the original typedef. If the compiler didn't croak there, then we would have redefined the typedef again in the __clang__ section. Yes, clang reports itself as gcc 4.2, so it sets __GNUC__ and __clang__. The patch I committed should be a no-op (except for gcc). http://stackoverflow.com/questions/28166565/detect-gcc-as-opposed-to-msvc-clang-with-macro #if defined(__FreeBSD__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif //- ... some lines later ... //- #if defined(__clang__) typedef void(*CoinSighandler_t)(int); # define CoinSighandler_t_defined #elif defined(__MACH__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif Ugh.. the problem is I am only looking at diffs, not at the code so I missed this mess. Second try: http://svn.apache.org/viewvc?view=revisionrevision=1690755 This part doesn't look right: #if defined(__FreeBSD__) defined(__GNUC__) - typedef __decltype(SIG_DFL) CoinSighandler_t; + typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif That's weird, I took the hunk from FreeBSD's port. patching file CoinMP-1.7.6/Osi/ltmain.sh patching file CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp /usr/local/bin/gpatch: malformed patch at line 1230: @@ -95,7 +95,10 @@ dmake: Error code 2, while making './unxfbsdx.pro/misc/build/so_patched_coinmp' 1 module(s): coinmp need(s) to be rebuilt Reason(s): I did notice the buildbot was failing on nss(?). That's what I get for taking hunks from elsewhere :-P. As you might have noticed I don't spend much quality time with AOO lately :-(. I patched the patch with this patch and got a successful coinmp build: Index: ext_libraries/coinmp/coinmp-1.7.6-clang.patch === --- ext_libraries/coinmp/coinmp-1.7.6-clang.patch (revision 1690824) +++ ext_libraries/coinmp/coinmp-1.7.6-clang.patch (working copy) @@ -1,22 +1,25 @@ misc/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp 2011-01-03 20:31:00.0 -0300 -+++ misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp 2014-02-01 02:02:10.596696644 -0300 -@@ -44,7 +44,7 @@ +--- misc/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp 2011-01-03 23:31:00.0 + misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp 2015-07-14 00:18:26.10536 + +@@ -43,7 +43,7 @@ + //- - #if defined(__FreeBSD__) defined(__GNUC__) -- typedef __decltype(SIG_DFL) CoinSighandler_t; -+ typedef typeof(SIG_DFL) CoinSighandler_t; +-#if defined(__FreeBSD__) defined(__GNUC__) ++#if defined(__FreeBSD__) defined(__GNUC__) !defined(__clang__) +typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif -@@ -95,7 +95,10 @@ +@@ -100,6 +100,13 @@ + # define CoinSighandler_t_defined + #endif - //- ++//- ++ ++#if defined(__clang__) ++ typedef __decltype(SIG_DFL) CoinSighandler_t; ++# define CoinSighandler_t_defined ++#endif ++ + //# --#if defined(__MACH__) defined(__GNUC__) -+#if !defined(__FreeBSD__) defined(__clang__) -+ typedef void(*CoinSighandler_t)(int); -+# define CoinSighandler_t_defined -+#elif defined(__MACH__) defined(__GNUC__) -typedef typeof(SIG_DFL) CoinSighandler_t; - # define CoinSighandler_t_defined - #endif + #ifndef CoinSighandler_t_defined Committed thanks. Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Are the Buildbots down?
On 07/13/15 11:29, Don Lewis wrote: ... OpenOffice has a clang patch that was not catching this. I hacked it for FreeBSD now: http://svn.apache.org/viewvc?view=revisionrevision=1690740 But there is certainly something wrong as clang is not being detected. I think clang defines __GNUC__, so with the existing clang patch we were still using the original typedef. If the compiler didn't croak there, then we would have redefined the typedef again in the __clang__ section. Yes, clang reports itself as gcc 4.2, so it sets __GNUC__ and __clang__. The patch I committed should be a no-op (except for gcc). http://stackoverflow.com/questions/28166565/detect-gcc-as-opposed-to-msvc-clang-with-macro #if defined(__FreeBSD__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif //- ... some lines later ... //- #if defined(__clang__) typedef void(*CoinSighandler_t)(int); # define CoinSighandler_t_defined #elif defined(__MACH__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif Ugh.. the problem is I am only looking at diffs, not at the code so I missed this mess. Second try: http://svn.apache.org/viewvc?view=revisionrevision=1690755 Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Are the Buildbots down?
On 13 Jul, Pedro Giffuni wrote:
On 07/13/15 02:06, Don Lewis wrote:
...
According to the bootstrap log, it's not a download problem.
I'm able to reproduce the problem here. It looks like clang doesn't
like some of the code in CoinMP:
In file included from ClpSolve.cpp:347:
/tmp/openoffice/aoo-4.2.0/ext_libraries/coinmp/unxfbsdx.pro/misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp:47:12:
error:
extension used [-Werror,-Wlanguage-extension-token]
typedef typeof(SIG_DFL) CoinSighandler_t;
^
The code fragment in question:
#if defined(__FreeBSD__) defined(__GNUC__)
typedef typeof(SIG_DFL) CoinSighandler_t;
# define CoinSighandler_t_defined
#endif
This has been changed in CoinMP-1.8.2 to:
#if defined(__FreeBSD__) defined(__GNUC__)
typedef __decltype(SIG_DFL) CoinSighandler_t;
# define CoinSighandler_t_defined
#endif
OpenOffice has a clang patch that was not catching this.
I hacked it for FreeBSD now:
http://svn.apache.org/viewvc?view=revisionrevision=1690740
But there is certainly something wrong as clang is not being detected.
I think clang defines __GNUC__, so with the existing clang patch we
were still using the original typedef. If the compiler didn't croak
there, then we would have redefined the typedef again in the __clang__
section.
http://stackoverflow.com/questions/28166565/detect-gcc-as-opposed-to-msvc-clang-with-macro
#if defined(__FreeBSD__) defined(__GNUC__)
typedef typeof(SIG_DFL) CoinSighandler_t;
# define CoinSighandler_t_defined
#endif
//-
#if defined(__NetBSD__) defined(__GNUC__)
typedef typeof(SIG_DFL) CoinSighandler_t;
# define CoinSighandler_t_defined
#endif
//-
#if defined(_AIX)
# if defined(__GNUC__)
typedef typeof(SIG_DFL) CoinSighandler_t;
# define CoinSighandler_t_defined
# endif
#endif
//-
#if defined (__hpux)
# define CoinSighandler_t_defined
# if defined(__GNUC__)
typedef typeof(SIG_DFL) CoinSighandler_t;
# else
extern C {
typedef void (*CoinSighandler_t) (int);
}
# endif
#endif
//-
#if defined(__sun)
# if defined(__SUNPRO_CC)
# include signal.h
extern C {
typedef void (*CoinSighandler_t) (int);
}
# define CoinSighandler_t_defined
# endif
# if defined(__GNUC__)
typedef typeof(SIG_DFL) CoinSighandler_t;
# define CoinSighandler_t_defined
# endif
#endif
//-
#if defined(__clang__)
typedef void(*CoinSighandler_t)(int);
# define CoinSighandler_t_defined
#elif defined(__MACH__) defined(__GNUC__)
typedef typeof(SIG_DFL) CoinSighandler_t;
# define CoinSighandler_t_defined
#endif
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Starting Introduction to Contributing to Apache OpenOffice Module
On 07/09/2015 12:49 PM, Mark Officer wrote: Hello, My name is Mark Officer and my background is in software product management/marketing and as such I would like to get involved in OpenOffice in these areas. I live in New Hampshire, US. Thank you, Mark Thanks for your interest in Apache OpenOffice, Mark. You seem to have an interesting mix of experience which we can surely use. Please feel free to ask questions or make suggestions on any of our mailing lists. We value your contributions. -- MzK Way down deep, we're all motivated by the same urges. Cats have the courage to live by them. -- Jim Davis - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Are the Buildbots down?
On 07/13/15 02:06, Don Lewis wrote: On 12 Jul, Pedro Giffuni wrote: Hi Gavin; Let me copy Don Lewis, who maintains the FreeBSD port @FreeBSD ... On 07/12/15 12:59, Gavin McDonald wrote: On 12 Jul 2015, at 4:50 pm, Pedro Giffuni p...@apache.org mailto:p...@apache.org wrote: Hello; On 07/11/15 10:39, Pedro Giffuni wrote: Hello; On 07/11/15 05:39, Marcus wrote: Am 07/11/2015 11:31 AM, schrieb Gavin McDonald: The ?open office-fbsd-nightly? fails the ?build ?all? step and needs investigating. 1 module(s): coinmp need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /usr/home/buildslave27/slave27/openoffice-fbsd-nightly/build/ext_libraries/coinmp When you have fixed the errors in that module you can resume the build by running: build --all:coinmp @Pedro: As FreeBSD is involved maybe you can give Gavin some help? I looked at it briefly but the buildbot offers little useful information. I have asked Don Lewis to look at it. He has been very helpful and is for most purposes the FreeBSD port maintainer these days. It may be a download error, but also the old FreeBSD version that is being used has a very old toolchain. I have no idea why you keep saying we are using a very old version, I have mentioned before: This is what the bb-fbsd2 buildbot slave is using: FreeBSD 10.1-RELEASE-p10 (GENERIC) #0: Wed May 13 06:54:13 UTC 2015 Can you tell me why you think we are on an older version? Gav? https://ci.apache.org/buildslaves/bb-fbsd2_64bit Reports: FreeBSD 9.0-RELEASE 64 bit buildbot for genberal projects use. Have you updated the compiler as I suggested previously? Perhaps there is some way to give Don access to the buildbot? He already signed an ICLA. According to the bootstrap log, it's not a download problem. I'm able to reproduce the problem here. It looks like clang doesn't like some of the code in CoinMP: In file included from ClpSolve.cpp:347: /tmp/openoffice/aoo-4.2.0/ext_libraries/coinmp/unxfbsdx.pro/misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp:47:12: error: extension used [-Werror,-Wlanguage-extension-token] typedef typeof(SIG_DFL) CoinSighandler_t; ^ The code fragment in question: #if defined(__FreeBSD__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif This has been changed in CoinMP-1.8.2 to: #if defined(__FreeBSD__) defined(__GNUC__) typedef __decltype(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif Hmm .. that change happened six years ago in the coin trunk: https://projects.coin-or.org/CoinUtils/changeset/1126/trunk/CoinUtils/src/CoinSignal.hpp But the coinmp guys haven't updated it. We carry the change in our (FreeBSD) local port: https://svnweb.freebsd.org/ports/head/math/coinmp/files/ Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Are the Buildbots down?
On 13 Jul, Pedro Giffuni wrote: On 07/13/15 02:06, Don Lewis wrote: On 12 Jul, Pedro Giffuni wrote: Hi Gavin; Let me copy Don Lewis, who maintains the FreeBSD port @FreeBSD ... On 07/12/15 12:59, Gavin McDonald wrote: On 12 Jul 2015, at 4:50 pm, Pedro Giffuni p...@apache.org mailto:p...@apache.org wrote: Hello; On 07/11/15 10:39, Pedro Giffuni wrote: Hello; On 07/11/15 05:39, Marcus wrote: Am 07/11/2015 11:31 AM, schrieb Gavin McDonald: The ?open office-fbsd-nightly? fails the ?build ?all? step and needs investigating. 1 module(s): coinmp need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /usr/home/buildslave27/slave27/openoffice-fbsd-nightly/build/ext_libraries/coinmp When you have fixed the errors in that module you can resume the build by running: build --all:coinmp @Pedro: As FreeBSD is involved maybe you can give Gavin some help? I looked at it briefly but the buildbot offers little useful information. I have asked Don Lewis to look at it. He has been very helpful and is for most purposes the FreeBSD port maintainer these days. It may be a download error, but also the old FreeBSD version that is being used has a very old toolchain. I have no idea why you keep saying we are using a very old version, I have mentioned before: This is what the bb-fbsd2 buildbot slave is using: FreeBSD 10.1-RELEASE-p10 (GENERIC) #0: Wed May 13 06:54:13 UTC 2015 Can you tell me why you think we are on an older version? Gav? https://ci.apache.org/buildslaves/bb-fbsd2_64bit Reports: FreeBSD 9.0-RELEASE 64 bit buildbot for genberal projects use. Have you updated the compiler as I suggested previously? Perhaps there is some way to give Don access to the buildbot? He already signed an ICLA. According to the bootstrap log, it's not a download problem. I'm able to reproduce the problem here. It looks like clang doesn't like some of the code in CoinMP: In file included from ClpSolve.cpp:347: /tmp/openoffice/aoo-4.2.0/ext_libraries/coinmp/unxfbsdx.pro/misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp:47:12: error: extension used [-Werror,-Wlanguage-extension-token] typedef typeof(SIG_DFL) CoinSighandler_t; ^ The code fragment in question: #if defined(__FreeBSD__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif This has been changed in CoinMP-1.8.2 to: #if defined(__FreeBSD__) defined(__GNUC__) typedef __decltype(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif Hmm .. that change happened six years ago in the coin trunk: https://projects.coin-or.org/CoinUtils/changeset/1126/trunk/CoinUtils/src/CoinSignal.hpp But the coinmp guys haven't updated it. We carry the change in our (FreeBSD) local port: https://svnweb.freebsd.org/ports/head/math/coinmp/files/ I looked at the PR and it appears that the FreeBSD port was patched to revert the typeof - __decltype upstream change so that the port would build with our ancient gcc in FreeBSD 8 and 9 base. Since the port successfully compiles with clang on FreeBSD 10, I suspect the difference between the FreeBSD port and building the openoffice bundled version must be caused by different compiler flags. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Are the Buildbots down?
On 07/13/15 02:06, Don Lewis wrote: ... According to the bootstrap log, it's not a download problem. I'm able to reproduce the problem here. It looks like clang doesn't like some of the code in CoinMP: In file included from ClpSolve.cpp:347: /tmp/openoffice/aoo-4.2.0/ext_libraries/coinmp/unxfbsdx.pro/misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp:47:12: error: extension used [-Werror,-Wlanguage-extension-token] typedef typeof(SIG_DFL) CoinSighandler_t; ^ The code fragment in question: #if defined(__FreeBSD__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif This has been changed in CoinMP-1.8.2 to: #if defined(__FreeBSD__) defined(__GNUC__) typedef __decltype(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif OpenOffice has a clang patch that was not catching this. I hacked it for FreeBSD now: http://svn.apache.org/viewvc?view=revisionrevision=1690740 But there is certainly something wrong as clang is not being detected. Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Mac Download
Hi There, I am getting an error from my computer now allowing me to open open office full download. How do I fix this? Brenda
Re: Are the Buildbots down?
On 13 Jul, Pedro Giffuni wrote: On 07/13/15 11:29, Don Lewis wrote: ... OpenOffice has a clang patch that was not catching this. I hacked it for FreeBSD now: http://svn.apache.org/viewvc?view=revisionrevision=1690740 But there is certainly something wrong as clang is not being detected. I think clang defines __GNUC__, so with the existing clang patch we were still using the original typedef. If the compiler didn't croak there, then we would have redefined the typedef again in the __clang__ section. Yes, clang reports itself as gcc 4.2, so it sets __GNUC__ and __clang__. The patch I committed should be a no-op (except for gcc). http://stackoverflow.com/questions/28166565/detect-gcc-as-opposed-to-msvc-clang-with-macro #if defined(__FreeBSD__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif //- ... some lines later ... //- #if defined(__clang__) typedef void(*CoinSighandler_t)(int); # define CoinSighandler_t_defined #elif defined(__MACH__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif Ugh.. the problem is I am only looking at diffs, not at the code so I missed this mess. Second try: http://svn.apache.org/viewvc?view=revisionrevision=1690755 This part doesn't look right: #if defined(__FreeBSD__) defined(__GNUC__) - typedef __decltype(SIG_DFL) CoinSighandler_t; + typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif patching file CoinMP-1.7.6/Osi/ltmain.sh patching file CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp /usr/local/bin/gpatch: malformed patch at line 1230: @@ -95,7 +95,10 @@ dmake: Error code 2, while making './unxfbsdx.pro/misc/build/so_patched_coinmp' 1 module(s): coinmp need(s) to be rebuilt Reason(s): I patched the patch with this patch and got a successful coinmp build: Index: ext_libraries/coinmp/coinmp-1.7.6-clang.patch === --- ext_libraries/coinmp/coinmp-1.7.6-clang.patch (revision 1690824) +++ ext_libraries/coinmp/coinmp-1.7.6-clang.patch (working copy) @@ -1,22 +1,25 @@ misc/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp 2011-01-03 20:31:00.0 -0300 -+++ misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp 2014-02-01 02:02:10.596696644 -0300 -@@ -44,7 +44,7 @@ +--- misc/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp 2011-01-03 23:31:00.0 + misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp 2015-07-14 00:18:26.10536 + +@@ -43,7 +43,7 @@ + //- - #if defined(__FreeBSD__) defined(__GNUC__) -- typedef __decltype(SIG_DFL) CoinSighandler_t; -+ typedef typeof(SIG_DFL) CoinSighandler_t; +-#if defined(__FreeBSD__) defined(__GNUC__) ++#if defined(__FreeBSD__) defined(__GNUC__) !defined(__clang__) +typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif -@@ -95,7 +95,10 @@ +@@ -100,6 +100,13 @@ + # define CoinSighandler_t_defined + #endif - //- ++//- ++ ++#if defined(__clang__) ++ typedef __decltype(SIG_DFL) CoinSighandler_t; ++# define CoinSighandler_t_defined ++#endif ++ + //# --#if defined(__MACH__) defined(__GNUC__) -+#if !defined(__FreeBSD__) defined(__clang__) -+ typedef void(*CoinSighandler_t)(int); -+# define CoinSighandler_t_defined -+#elif defined(__MACH__) defined(__GNUC__) -typedef typeof(SIG_DFL) CoinSighandler_t; - # define CoinSighandler_t_defined - #endif + #ifndef CoinSighandler_t_defined - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Mac Download
On 2015-07-13, 1:45 PM Brenda Daykin wrote concerning Mac Download: I am getting an error from my computer now allowing me to open open office full download. How do I fix this? See this article from Apple: OS X: About Gatekeeper: https://support.apple.com/en-ca/HT202491 -- 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 dev@openoffice.apache.org - 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
Re: Are the Buildbots down?
On 12 Jul, Pedro Giffuni wrote: Hi Gavin; Let me copy Don Lewis, who maintains the FreeBSD port @FreeBSD ... On 07/12/15 12:59, Gavin McDonald wrote: On 12 Jul 2015, at 4:50 pm, Pedro Giffuni p...@apache.org mailto:p...@apache.org wrote: Hello; On 07/11/15 10:39, Pedro Giffuni wrote: Hello; On 07/11/15 05:39, Marcus wrote: Am 07/11/2015 11:31 AM, schrieb Gavin McDonald: The ?open office-fbsd-nightly? fails the ?build ?all? step and needs investigating. 1 module(s): coinmp need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /usr/home/buildslave27/slave27/openoffice-fbsd-nightly/build/ext_libraries/coinmp When you have fixed the errors in that module you can resume the build by running: build --all:coinmp @Pedro: As FreeBSD is involved maybe you can give Gavin some help? I looked at it briefly but the buildbot offers little useful information. I have asked Don Lewis to look at it. He has been very helpful and is for most purposes the FreeBSD port maintainer these days. It may be a download error, but also the old FreeBSD version that is being used has a very old toolchain. I have no idea why you keep saying we are using a very old version, I have mentioned before: This is what the bb-fbsd2 buildbot slave is using: FreeBSD 10.1-RELEASE-p10 (GENERIC) #0: Wed May 13 06:54:13 UTC 2015 Can you tell me why you think we are on an older version? Gav? https://ci.apache.org/buildslaves/bb-fbsd2_64bit Reports: FreeBSD 9.0-RELEASE 64 bit buildbot for genberal projects use. Have you updated the compiler as I suggested previously? Perhaps there is some way to give Don access to the buildbot? He already signed an ICLA. According to the bootstrap log, it's not a download problem. I'm able to reproduce the problem here. It looks like clang doesn't like some of the code in CoinMP: In file included from ClpSolve.cpp:347: /tmp/openoffice/aoo-4.2.0/ext_libraries/coinmp/unxfbsdx.pro/misc/build/CoinMP-1.7.6/CoinUtils/src/CoinSignal.hpp:47:12: error: extension used [-Werror,-Wlanguage-extension-token] typedef typeof(SIG_DFL) CoinSighandler_t; ^ The code fragment in question: #if defined(__FreeBSD__) defined(__GNUC__) typedef typeof(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif This has been changed in CoinMP-1.8.2 to: #if defined(__FreeBSD__) defined(__GNUC__) typedef __decltype(SIG_DFL) CoinSighandler_t; # define CoinSighandler_t_defined #endif Also, the buildbot errors are kind of random: https://ci.apache.org/builders/openoffice-fbsd-nightly/builds/0/steps/build%20--all/logs/stdio fails coinmp. https://ci.apache.org/builders/openoffice-fbsd-nightly/builds/1/steps/build%20--all/logs/stdio fails curl. https://ci.apache.org/builders/openoffice-fbsd-nightly/builds/2/steps/build%20--all/logs/stdio fails coinmp. https://ci.apache.org/builders/openoffice-fbsd-nightly/builds/3/steps/build%20--all/logs/stdio fails coinmp. https://ci.apache.org/builders/openoffice-fbsd-nightly/builds/4/steps/build%20--all/logs/stdio fails nss. The build order seems to vary from run to run, so maybe all three are broken and we're just seeing the first failure. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Are the Buildbots down?
Just for giggles, I tried build --from nss and got this: make[2]: Entering directory '/tmp/openoffice/aoo-4.2.0/main/nss/unxfbsdx.pro/misc/build/nss-3.14.4/mozilla/security/coreconf/nsinstall' gcc -o out/nsinstall.o -c -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DUSE_UTIL_DIRECTLY -I/usr/X11R6/include -I../../../dist/out/include -I../../../dist/public/coreconf -I../../../dist/private/coreconf nsinstall.c gmake[2]: gcc: Command not found ../../coreconf/rules.mk:389: recipe for target 'out/nsinstall.o' failed It shouldn't be trying to use gcc, which isn't installed here. I also tried build --from curl and it seemed to build properly. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE] Contents of OpenOffice 4.1.2
Hi I agree to use this as the overall plan, which of course needs to detailed. I do have a comment about digital signing. It is correct than I do not have spare cycles before mid october. Digital signing means in reality white listing the content, which are both our exe as well as many third part DLLs (some of the libraries are statically linked and not exposed outside the exe). Most of our third party libraries are pretty old (but works well for our purpose), and some of them have known security isses (not in the parts AOO uses). We need to upgrade the libraries that uses a DLL, otherwise we might whitelist a DLL with known security issues. This process is something we should do ahead of every release, and is not as such part of the digital signing, but digital signing makes it much more important. rgds jan I. On Sunday, July 12, 2015, Marcus marcus.m...@wtnet.de wrote: Am 07/12/2015 03:57 PM, schrieb Andrea Pescetti: It's time to decide what goes into 4.1.2 and what doesn't. Not in terms of specific bugfixes (we have the standard process of nominating release blockers for this and I don't plan to change it), but in terms of categories. The following is a realistic list of what we can have in 4.1.2. Shall we take it as the overall plan for 4.1.2? In general I see it the same way. Some comments inline. 2. Features * Windows 10: Millions of our users will run Windows 10 within a few weeks. OpenOffice is reported to work smoothly on Windows 10 pre-releases. Should any major Windows 10 incompatibilities appear, they should be fixed in 4.1.2. When we want to react on specific bug reports (we should do this in any case as Windows is still the most favorite platform) then we create automatically a release schedule of a few weeks after that date - which is for me late summer. Just to be sure we understand the same. BTW: Release date of Win10 is July, 29th. 3. Localization * Existing translations: Pootle is now tracking the 4.2.0 release, so translators do not have an immediate way to fix translations for 4.1.2. There is a possibility to check whether we can reuse the 4.2.0 strings for 4.1.2, but due to the version clash I would prefer to fix strings upon request, in the SDF files directly and only in the case of major, well-defined bugs (example: the Italian version has a typo in a main menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file manually to fix it for the 4.1.x line). This has also the advantage (when we don't get too many change requests) that we know in detail what is changing. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Sent from My iPad, sorry for any misspellings.
Re: [RELEASE] Contents of OpenOffice 4.1.2
With regards to digital signing, we have ‘test’ credits that can be used to practice on. Gav… On 13 Jul 2015, at 9:04 am, jan i j...@apache.org wrote: Hi I agree to use this as the overall plan, which of course needs to detailed. I do have a comment about digital signing. It is correct than I do not have spare cycles before mid october. Digital signing means in reality white listing the content, which are both our exe as well as many third part DLLs (some of the libraries are statically linked and not exposed outside the exe). Most of our third party libraries are pretty old (but works well for our purpose), and some of them have known security isses (not in the parts AOO uses). We need to upgrade the libraries that uses a DLL, otherwise we might whitelist a DLL with known security issues. This process is something we should do ahead of every release, and is not as such part of the digital signing, but digital signing makes it much more important. rgds jan I. On Sunday, July 12, 2015, Marcus marcus.m...@wtnet.de wrote: Am 07/12/2015 03:57 PM, schrieb Andrea Pescetti: It's time to decide what goes into 4.1.2 and what doesn't. Not in terms of specific bugfixes (we have the standard process of nominating release blockers for this and I don't plan to change it), but in terms of categories. The following is a realistic list of what we can have in 4.1.2. Shall we take it as the overall plan for 4.1.2? In general I see it the same way. Some comments inline. 2. Features * Windows 10: Millions of our users will run Windows 10 within a few weeks. OpenOffice is reported to work smoothly on Windows 10 pre-releases. Should any major Windows 10 incompatibilities appear, they should be fixed in 4.1.2. When we want to react on specific bug reports (we should do this in any case as Windows is still the most favorite platform) then we create automatically a release schedule of a few weeks after that date - which is for me late summer. Just to be sure we understand the same. BTW: Release date of Win10 is July, 29th. 3. Localization * Existing translations: Pootle is now tracking the 4.2.0 release, so translators do not have an immediate way to fix translations for 4.1.2. There is a possibility to check whether we can reuse the 4.2.0 strings for 4.1.2, but due to the version clash I would prefer to fix strings upon request, in the SDF files directly and only in the case of major, well-defined bugs (example: the Italian version has a typo in a main menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file manually to fix it for the 4.1.x line). This has also the advantage (when we don't get too many change requests) that we know in detail what is changing. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Sent from My iPad, sorry for any misspellings. Gav... (( ( ( )\ ) )\ ) )\ ) ( )) )\(()/((()/( (()/( )\ ) ( ) ( /( ( (( /( ( ( ( _)( /(_))/(_)) /(_)) ( (()/( )( ( /( ( )\()))())\ ( )\()) ))\ )())\ )\ _ )\ (_)) (_))_| (_)) )\ ) /(_))(()\ )(_)) )\ (_))/(()\ /((_) )\ (_))/ /((_)(()\ /((_) (_)_\(_)/ __|| |_ |_ _| _(_/((_) _| ((_)((_)_ ((_)| |_ ((_)(_))( ((_)| |_ (_))( ((_)(_)) / _ \ \__ \| __| | | | ' \))| _|| '_|/ _` |(_-| _|| '_|| || |/ _| | _|| || || '_|/ -_) /_/ \_\ |___/|_||___||_||_| |_| |_| \__,_|/__/ \__||_| \_,_|\__| \__| \_,_||_| \___|
