blaze 3.4 won't compile

Issue #195 resolved created an issue

Hello -

I am getting this error when building with the latest release:

/home/khuck/src/phylanx/tools/buildbot/src/blaze-head/blaze/math/typetraits/IsMatReduceExpr.h:68:49: error: type/value mismatch at argument 1 in template parameter list for ‘template<class VT, long unsigned int RF> struct blaze::MatReduceExpr’
    static TrueType test( const MatReduceExpr<N,U>& );

Comments (7)

  1. reporter

    I should add that this is with GCC 7.1 on an x86_64 system, and the compilation line that is failing is:

    /usr/bin/g++ -DBLAZE_USE_HPX_THREADS -DBOOST_DISABLE_ASSERTS -DHPX_COMPONENT_EXPORTS -DHPX_COMPONENT_NAME=hpx_phylanx -DHPX_COMPONENT_STRING=\"hpx_phylanx\" -DHPX_DISABLE_ASSERTS -DPHYLANX_EXPORTS -Dphylanx_component_EXPORTS -I/home/khuck/src/phylanx -isystem /home/khuck/src/phylanx/tools/buildbot/src/hpx -isystem /home/khuck/src/phylanx/tools/buildbot/src/hpx/apex/src/apex -isystem /home/khuck/src/phylanx/tools/buildbot/build-omegalinux-x86_64-Linux-gcc/hpx-Release -isystem /home/khuck/src/phylanx/tools/buildbot/src/hpx/examples -isystem /home/khuck/src/phylanx/tools/buildbot/src/hpx/tests -I/home/khuck/src/phylanx/tools/buildbot/build-omegalinux-x86_64-Linux-gcc/phylanx-Release -isystem /home/khuck/src/phylanx/tools/buildbot/src/blaze-head -fdiagnostics-show-option -Werror=vla -Werror=return-type -Wno-unused-but-set-parameter -Wno-unused-but-set-variable -Wno-unused-local-typedefs -Wno-sync-nand -Wno-delete-non-virtual-dtor -O3 -DNDEBUG -fPIC -std=c++17 -std=gnu++14 -o CMakeFiles/phylanx_component.dir/ast/detail/is_function_call.cpp.o -c /home/khuck/src/phylanx/src/ast/detail/is_function_call.cpp

  2. Klaus Iglberger


    Thanks for pointing this out. This is indeed a major oversight on our side and we apologize for the inconvenience. We have already pushed the fix.

    Best regards,


  3. Klaus Iglberger

    Commit bbe39c8 fixes the IsMatReduceExpr type trait, which is causing this compilation error. The fix is immediately available via cloning the Blaze repository and will be officially released in Blaze 3.5.

  4. Klaus Iglberger

    Due to the severity of the problem we have decided to integrate the fix into Blaze 3.4 directly. Thus we have moved the v3.4 tag by one commit and replaced the download files. Again, we apologize to everyone who ran into this problem.

  5. Log in to comment