Re: building with gcc 10 and external (system) boost

2021-06-20 Thread Yury Tarasievich
Right, understandable. Only I believe there's need to consider also that the newer GCC (10.3.0 in my case) can't (won't?) compile even the headers-only part of older boost (1.55, the internal one). Maybe there're issues with other libraries frozen at their older versions, too. -Yury

Re: building with gcc 10 and external (system) boost

2021-06-20 Thread Don Lewis
On 20 Jun, Yury Tarasievich wrote: > Hello Peter, > > You are right on both issues, of course. > > To be fair, on your (1), I didn't touch that > variable check, I just brute-forced the C++11 > mode of compilation. > > Which leads to your (2), but thing is, modern > boost sort of requires

Re: building with gcc 10 and external (system) boost

2021-06-20 Thread Peter Kovacs
On 20.06.21 07:40, Yury Tarasievich wrote: Hello Peter, Which leads to your (2), but thing is, modern boost sort of requires C++11. Might be other external modules do, too. Might that switch to C++11 be overdue? I would like to switch. I am a big fan of C++11, but I am worried on the

[GitHub] [openoffice] leginee commented on pull request #133: graphite: remove the -Werror option from debug builds

2021-06-20 Thread GitBox
leginee commented on pull request #133: URL: https://github.com/apache/openoffice/pull/133#issuecomment-864513194 Then we have 2 choices. Fix the Issues or prepare the switch to a replacement. -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: building with gcc 10 and external (system) boost

2021-06-20 Thread Peter Kovacs
On 20.06.21 08:57, Don Lewis wrote: On 20 Jun, Yury Tarasievich wrote: Hello Peter, You are right on both issues, of course. To be fair, on your (1), I didn't touch that variable check, I just brute-forced the C++11 mode of compilation. Which leads to your (2), but thing is, modern boost

[GitHub] [openoffice] DonLewisFreeBSD commented on pull request #133: graphite: remove the -Werror option from debug builds

2021-06-20 Thread GitBox
DonLewisFreeBSD commented on pull request #133: URL: https://github.com/apache/openoffice/pull/133#issuecomment-864508440 > The meaing of the Flag is > -Werror: every warning is treated as an error. > > Since Grafite is a dependency it is fine to build without. However Imho we

Re: [GitHub] [openoffice] ardovm edited a comment on pull request #133: graphite: remove the -Werror option from debug builds

2021-06-20 Thread Pedro Lino
Hi Arrigo, all Development seems to be quite live at https://github.com/silnrsi/graphite Regards, Pedro > On 06/20/2021 9:08 PM GitBox wrote: > > > ardovm edited a comment on pull request #133: > URL: https://github.com/apache/openoffice/pull/133#issuecomment-864605285 > > >The first

[GitHub] [openoffice] ardovm edited a comment on pull request #133: graphite: remove the -Werror option from debug builds

2021-06-20 Thread GitBox
ardovm edited a comment on pull request #133: URL: https://github.com/apache/openoffice/pull/133#issuecomment-864605285 The first two warnings are IMHO bugs. The first one is a function parameter type `bool` instead of `bool&` and the second is a mixup of return values in a `switch`

[GitHub] [openoffice] ardovm commented on pull request #133: graphite: remove the -Werror option from debug builds

2021-06-20 Thread GitBox
ardovm commented on pull request #133: URL: https://github.com/apache/openoffice/pull/133#issuecomment-864605285 The first two warnings are IMHO bugs. The first one is a function parameter type `bool` instead of `bool&` and the second is a mixup of return values in a `switch` statement.

Re: [GitHub] [openoffice] ardovm edited a comment on pull request #133: graphite: remove the -Werror option from debug builds

2021-06-20 Thread Don Lewis
On 20 Jun, Pedro Lino wrote: > Hi Arrigo, all > > Development seems to be quite live at > https://github.com/silnrsi/graphite We are using SIL Graphite, http://silgraphite.sourceforge.net/ Looking at the Graphite technical overview page mentioned here: