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 that switch to C++11 be overdue?
What I consider the nicest result (beyond the
'fact of the pudding') is seeing that the C++11
build is achievable with very minimal changes to
the source, which wouldn't (shouldn't?) reflect
on builds with older versions of GCC.
PS The JDK I compiled with was Oracle's 1.8.0_271.
PPS There were tons of warnings about 'dynamic
exception throw declarations'. Literally
everywhere. Otherwise the compiler didn't
complain overmuch, AFAICT.
PPPS The build system is a conundrum in an
enigma. Or something. Did anyone wonder how the
following worked for me?
--disable-category-b \
--enable-hyphen \
--enable-hunspell \
--disable-coinmp \
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
