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

2021-06-19 Thread Peter Kovacs
This issue occurs because your Boost library is to new, and the fallback case has been selected (as in /d/home/ty/c/+ooo/aoo45/main/solver/450/unxlngx6.pro/inc/stl/vector ) Maybe this is more an issue of autoconf? My build on Arch Linux stopped working because of needed changes due to a

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

2021-06-19 Thread Yury Tarasievich
On 2021/06/18 07:08:17, Yury Tarasievich wrote ... I've managed to actually finish the build with the changes: https://gist.github.com/yurytch/9725e3281f9ef784cbf865fcebf51517 (plus some info in two comments) This is of course a kludge cubed, but at the moment it seems to serve. I didn't

[GitHub] [openoffice] Pilot-Pirx merged pull request #15: Issue 97058 - Add Fontwork into Insert menu

2021-06-19 Thread GitBox
Pilot-Pirx merged pull request #15: URL: https://github.com/apache/openoffice/pull/15 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service,

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

2021-06-19 Thread GitBox
ardovm opened a new pull request #133: URL: https://github.com/apache/openoffice/pull/133 The flag is set by default by the graphite configure script, but it lets the compilation fail with gcc 7.5 The compilation of the graphite module is consistently failing on openSUSE Leap 15.2

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

2021-06-19 Thread GitBox
leginee commented on pull request #133: URL: https://github.com/apache/openoffice/pull/133#issuecomment-864492889 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 should strife for

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

2021-06-19 Thread Peter Kovacs
Hi Yuri, Nice work! However there is more then One change I am unsure about. # you removed the __cplusplus string check. I think that is a bit hacky. It would have benn better to check the content and add it with or # switching to C11 -> we should do this and start refactoring the code to

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

2021-06-19 Thread Yury Tarasievich
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 C++11. Might be other external modules do, too. Might