Hi, this seems to be caused by /usr/bin/c++ accepting flags during cmake configuration, but not later during compilation. ranges uses the check_cxx_compiler_flag in order to set a lot of flags, including the ones mentioned by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926218#5
Using the c++98-compat as an example: cmake executes /usr/bin/c++ -Wno-c++98-compat ..../range-v3/build/CMakeFiles/CMakeTmp/src.cxx -o .... to see if no-c++98-compat is supported. But c++ accepts even nonexistant warnings: touch empty.cpp /usr/bin/c++ -Wno-iamsurethisonedoesnotexist -c empty.cpp -o /dev/null works fine, even if the following gives (as expected) an error: /usr/bin/c++ -Wiamsurethisonedoesnotexist -c empty.cpp -o /dev/null c++: error: unrecognized command line option ‘-Wiamsurethisonedoesnotexist’ so I would say this it not ranges that is broken, it's gcc. I would say that the proper action (for the ranges package) is to drop the Werror from line 34 in cmake/ranges_flags.cmake makes the build pass. Paul -- Paul Dreik Web: https://www.pauldreik.se/ Phone: +46 (0)73 99 26 333 Alt. voice channels: Signal, Whatsapp
signature.asc
Description: OpenPGP digital signature