Bug#957475: libreoffice: ftbfs with GCC-10

[Rene Engelhard <rene@debian.org>]

clone 957475 -1
reassign -1 src:boost1.67
notforwarded -1
block 957475 by -1
retitle 957475 boost1.67 needs fixes for gcc 10
thanks

Hi,

On Fri, Apr 17, 2020 at 11:04:54AM +0000, Matthias Klose wrote:
> [build CXX] vcl/source/window/menuitemlist.cxx
> In file included from /<<PKGBUILDDIR>>/vcl/source/window/layout.cxx:21:
> /usr/include/boost/multi_array.hpp: In instantiation of ‘void boost::multi_array<T, NumDims, Allocator>::allocate_space() [with T = GridEntry; long unsigned int NumDims = 2; Allocator = std::allocator<GridEntry>]’:
> /usr/include/boost/multi_array.hpp:148:5:   required from ‘boost::multi_array<T, NumDims, Allocator>::multi_array() [with T = GridEntry; long unsigned int NumDims = 2; Allocator = std::allocator<GridEntry>]’
> /<<PKGBUILDDIR>>/vcl/source/window/layout.cxx:819:16:   required from here
> /usr/include/boost/multi_array.hpp:478:39: error: no type named ‘const_pointer’ in ‘class std::allocator<GridEntry>’
>   478 |     typename Allocator::const_pointer no_hint=0;
>       |                                       ^~~~~~~
> /usr/include/boost/multi_array.hpp:478:39: error: no type named ‘const_pointer’ in ‘class std::allocator<GridEntry>’
> /usr/include/boost/multi_array.hpp: In instantiation of ‘void boost::multi_array<T, NumDims, Allocator>::deallocate_space() [with T = GridEntry; long unsigned int NumDims = 2; Allocator = std::allocator<GridEntry>]’:
> /usr/include/boost/multi_array.hpp:473:5:   required from ‘boost::multi_array<T, NumDims, Allocator>::~multi_array() [with T = GridEntry; long unsigned int NumDims = 2; Allocator = std::allocator<GridEntry>]’
> /<<PKGBUILDDIR>>/vcl/source/window/layout.cxx:819:16:   required from here
> /usr/include/boost/multi_array.hpp:488:20: error: ‘class std::allocator<GridEntry>’ has no member named ‘destroy’
>   488 |         allocator_.destroy(i);
>       |         ~~~~~~~~~~~^~~~~~~

This complains about stuff inside a boost header i(which is header-only
here)...

And indeed, building with boost 1.71 does NOT give the error. So Debians
old default boost strikes again. Either boost1.67 needs to be fixed or
the default changed before gcc 10.

Regards,

Rene