Bug#984049: enblend-enfuse: ftbfs with GCC-11

[Andreas Tille]

Control: tags -1 help

Hi,

Am Tue, Dec 14, 2021 at 06:27:47PM +0100 schrieb Heinz Repp:
> > /usr/include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17 does not allow dynamic exception specifications
> > /usr/include/vigra/stdconvolution.hxx:796:13: error: ISO C++17 does not allow dynamic exception specifications
> 
> For those two errors I propose the first patch (c++17conf, in
> include/vigra): The original code had conditional compilation in place: all
> non Microsoft compilers got a pre-C++11 and C++17-forbidden construct, and
> Microsoft Visual C++ 2014 and up got a C++11-introduced and C++17-conformant
> construct. I removed the condition and left only the latter - this means you
> need at least GCC 4.8.1 to compile this (or MSC 2014/201).

I applied this patch in Git and it seems that it helps to build this
package.
 
> 
> Then I found another syntax error in Python code - Python 3.10 requires
> parentheses around multiple except-clauses (pythonexcept, in vigranumpy).

This patch does not apply (the ',' was replaced by 'as' which is also
valid).
 
> With those two patches it compiles, but then 22 tests fail, all with the
> same error in C++ template syntax I am not familiar with. They all fail
> because of a single discrepancy between Python and C++ representation of the
> constructArrayFromAxistags function:
> 
> > Boost.Python.ArgumentError: Python argument types in
> >     vigra.vigranumpycore.constructArrayFromAxistags(type, tuple, numpy.dtype[float32], AxisTags, bool)
> > did not match C++ signature:
> >     constructArrayFromAxistags(boost::python::api::object, vigra::ArrayVector<long, std::allocator<long> >, NPY_TYPES, vigra::AxisTags, bool)

I can confirm these test issues.  Any help would be welcome.
 
Kind regards

     Andreas.

-- 
http://fam-tille.de