Re: C++ standard when building OpenOffice

2019-11-05 Thread Damjan Jovanovic
On Tue, Nov 5, 2019 at 10:05 PM Don Lewis wrote: > > I thought that Damjan implemenented that. > > I have a patch that does gstreamer-1.0 access through run-time dynamic linking, so we should in theory just need the gstreamer source for its header files at compile time. It hasn't been tested or

Re: what is this supposed to do?

2019-11-05 Thread Don Lewis
On 5 Nov, Peter Kovacs wrote: > I am not sure why, but if you use gcc++98 std it compiles. Maybe it > optimizes the code since it might be dead code. It breaks the build in any mode for me with gcc9. I vaguely remember running across this code before, maybe with clang after it's default

Re: C++ standard when building OpenOffice

2019-11-05 Thread Don Lewis
On 5 Nov, Pedro Giffuni wrote: > Hi; > > Some notes, which I don't expect will be particularly useful ... > > - I recall one of the reasons for using Boost and not the native STL was > that the old MSVC compiler (the one AOO still uses) is poor on standards > compliance. It may be that the

Re: C++ standard when building OpenOffice

2019-11-05 Thread Pedro Giffuni
Hi; Some notes, which I don't expect will be particularly useful ... - I recall one of the reasons for using Boost and not the native STL was that the old MSVC compiler (the one AOO still uses) is poor on standards compliance. It may be that the internal Boost can be updated a bit more but

Re: C++ standard when building OpenOffice

2019-11-05 Thread Don Lewis
On 5 Nov, Jim Jagielski wrote: > > >> On Nov 5, 2019, at 1:56 PM, Don Lewis wrote: >> >> On 5 Nov, Matthias Seidel wrote: 4.1.x. >>> >>> To my knowledge we build 4.2.x on CentOS 7. > > Yep. > >> >> It builds and works fine on CentOS 6 as well. > > The issue is gstreamer1, as

Re: C++ standard when building OpenOffice

2019-11-05 Thread Don Lewis
On 5 Nov, Jim Jagielski wrote: > I am curious what system you build and test these patches on before > you commit... Thx! CentOS 6, Debian 9, FreeBSD 11, and Windows 7. Sometimes CentOS 7, Ubuntu 16 and FreeBSD as well. A mix of 32 and 64 bit.

Re: [DISCUSSION] Build environment future

2019-11-05 Thread Jim Jagielski
Before we start reworking the build environment to pieces, could we look at possibly doing a 4.2.0 release 1st? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:

Re: C++ standard when building OpenOffice

2019-11-05 Thread Jim Jagielski
I am curious what system you build and test these patches on before you commit... Thx! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: C++ standard when building OpenOffice

2019-11-05 Thread Jim Jagielski
> On Nov 5, 2019, at 1:56 PM, Don Lewis wrote: > > On 5 Nov, Matthias Seidel wrote: >>> >>> 4.1.x. >> >> To my knowledge we build 4.2.x on CentOS 7. Yep. > > It builds and works fine on CentOS 6 as well. The issue is gstreamer1, as well as other dependencies... as noted at

Re: what is this supposed to do?

2019-11-05 Thread Peter Kovacs
I am not sure why, but if you use gcc++98 std it compiles. Maybe it optimizes the code since it might be dead code. I rewrote the whole code, and used one class instead of 4 macros that copy paste from each other. I can post the code. But I do not know how to test or apply it into the rest. :P

Re: [DISCUSSION] Build environment future

2019-11-05 Thread Don Lewis
I'd like to see build.pl go away and switch to gmake at the top level. build.pl is bloated with a lot of stuff that we don't use and gets in the way of efficient parallel builds. Sometimes we don't have N modules that we can build at the same time, so it would be nice to be able to use the extra

Re: what is this supposed to do?

2019-11-05 Thread Branko Čibej
On 05.11.2019 19:54, Don Lewis wrote: > I don't understand what this strange little bit of code (line 611 of > basebmp/inc/basebmp/packedpixeliterator.hxx) is supposed to do: > > value_type get(difference_type const & d) const > { > const int remainder( x(d.x) %

Re: C++ standard when building OpenOffice

2019-11-05 Thread Don Lewis
On 4 Nov, Don Lewis wrote: > On 3 Nov, Don Lewis wrote: >> For much of our history, until fairly recently, the versions of gcc that >> we used defaulted to -std=gnu++98 when compiiling C++ code. >> >> When FreeBSD on i386 and amd64 switched from gcc to clang, it also >> defaulted to

Re: C++ standard when building OpenOffice

2019-11-05 Thread Don Lewis
On 5 Nov, Matthias Seidel wrote: > Hi Don, > > Am 05.11.19 um 19:02 schrieb Don Lewis: >> On 5 Nov, Peter Kovacs wrote: >>> what if we require LLVM as build requirement and build OpenOffice only >>> with LLVM instead of preinstalled gcc? >>> >>> the project provides packages for Windows, Linux

what is this supposed to do?

2019-11-05 Thread Don Lewis
I don't understand what this strange little bit of code (line 611 of basebmp/inc/basebmp/packedpixeliterator.hxx) is supposed to do: value_type get(difference_type const & d) const { const int remainder( x(d.x) % num_intraword_positions ); ^^

Re: C++ standard when building OpenOffice

2019-11-05 Thread Matthias Seidel
Hi Don, Am 05.11.19 um 19:02 schrieb Don Lewis: > On 5 Nov, Peter Kovacs wrote: >> what if we require LLVM as build requirement and build OpenOffice only >> with LLVM instead of preinstalled gcc? >> >> the project provides packages for Windows, Linux (And here RHEL 7.4) and >> mac. Cygwin offers

Re: C++ standard when building OpenOffice

2019-11-05 Thread Don Lewis
On 5 Nov, Peter Kovacs wrote: > what if we require LLVM as build requirement and build OpenOffice only > with LLVM instead of preinstalled gcc? > > the project provides packages for Windows, Linux (And here RHEL 7.4) and > mac. Cygwin offers Version 8.01 > > Debian offers also LLVM as Version

Re: C++ standard when building OpenOffice

2019-11-05 Thread Jim Jagielski
FWIW, macOS is clang, llvm, etc... it only pretends to be gcc :) > On Nov 5, 2019, at 1:44 AM, Peter Kovacs wrote: > > what if we require LLVM as build requirement and build OpenOffice only > with LLVM instead of preinstalled gcc? > > the project provides packages for Windows, Linux (And here

Re: C++ standard when building OpenOffice

2019-11-05 Thread Peter
It seems llvm provides 8.0 llvm builds: https://apt.llvm.org/ I am irritated they say it is nightly. But I am unsure what version 8 might have. Am 5. November 2019 10:19:56 MEZ schrieb Mechtilde : >Hello, > >Am 05.11.19 um 07:44 schrieb Peter Kovacs: >> what if we require LLVM as build

Fwd: Open Office not responding

2019-11-05 Thread Matthias Seidel
Hi all, This problem may be related to the "lost translations" in NSIS: https://bz.apache.org/ooo/show_bug.cgi?id=127628 Users are often confused and extract into the programs folder... It would be great if we can fix this for 4.1.8. Regards,    Matthias Weitergeleitete Nachricht

Re: C++ standard when building OpenOffice

2019-11-05 Thread Mechtilde
Hello, Am 05.11.19 um 07:44 schrieb Peter Kovacs: > what if we require LLVM as build requirement and build OpenOffice only > with LLVM instead of preinstalled gcc? > > the project provides packages for Windows, Linux (And here RHEL 7.4) and > mac. Cygwin offers Version 8.01 > > Debian offers