[Debian-med-packaging] Bug#976480: xenium: FTBFS: utils.hpp:80:4: error: #error "Unsupported compiler"

[Lucas Nussbaum]

Source: xenium
Version: 0.0.2+ds-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> /usr/bin/c++ -DDEBUG -I/<<PKGBUILDDIR>>/. -isystem /usr/src/googletest/googletest -isystem /usr/src/googletest/googletest/include -fsanitize=thread -o CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest-all.cc.o -c /usr/src/googletest/googletest/src/gtest-all.cc
> In file included from /<<PKGBUILDDIR>>/./xenium/marked_ptr.hpp:9,
>                  from /<<PKGBUILDDIR>>/./xenium/reclamation/detail/concurrent_ptr.hpp:9,
>                  from /<<PKGBUILDDIR>>/./xenium/reclamation/generic_epoch_based.hpp:9,
>                  from /<<PKGBUILDDIR>>/benchmarks/reclaimers.hpp:4,
>                  from /<<PKGBUILDDIR>>/benchmarks/hash_maps.hpp:3,
>                  from /<<PKGBUILDDIR>>/benchmarks/hash_map_benchmark.cpp:4:
> /<<PKGBUILDDIR>>/./xenium/utils.hpp:80:4: error: #error "Unsupported compiler"
>    80 |   #error "Unsupported compiler"
>       |    ^~~~~
> In file included from /<<PKGBUILDDIR>>/./xenium/backoff.hpp:9,
>                  from /<<PKGBUILDDIR>>/./xenium/vyukov_hash_map.hpp:10,
>                  from /<<PKGBUILDDIR>>/benchmarks/hash_maps.hpp:11,
>                  from /<<PKGBUILDDIR>>/benchmarks/hash_map_benchmark.cpp:4:
> /<<PKGBUILDDIR>>/./xenium/detail/hardware.hpp:25:6: warning: #warning "No hardware_pause implementation available - falling back to local volatile noop." [-Wcpp]
>    25 |     #warning "No hardware_pause implementation available - falling back to local volatile noop."
>       |      ^~~~~~~
> In file included from /<<PKGBUILDDIR>>/./xenium/marked_ptr.hpp:9,
>                  from /<<PKGBUILDDIR>>/./xenium/reclamation/detail/concurrent_ptr.hpp:9,
>                  from /<<PKGBUILDDIR>>/./xenium/reclamation/generic_epoch_based.hpp:9,
>                  from /<<PKGBUILDDIR>>/benchmarks/reclaimers.hpp:4,
>                  from /<<PKGBUILDDIR>>/benchmarks/hash_maps.hpp:3,
>                  from /<<PKGBUILDDIR>>/benchmarks/hash_map_benchmark.cpp:4:
> /<<PKGBUILDDIR>>/./xenium/utils.hpp: In function ‘uint64_t xenium::utils::random()’:
> /<<PKGBUILDDIR>>/./xenium/utils.hpp:84:12: error: ‘getticks’ was not declared in this scope; did you mean ‘gettid’?
>    84 |     return getticks() >> 4;
>       |            ^~~~~~~~
>       |            gettid
> [ 14%] Building CXX object CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest_main.cc.o
> /usr/bin/c++ -DDEBUG -I/<<PKGBUILDDIR>>/. -isystem /usr/src/googletest/googletest -isystem /usr/src/googletest/googletest/include -fsanitize=thread -o CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest_main.cc.o -c /usr/src/googletest/googletest/src/gtest_main.cc
> [ 17%] Linking CXX static library libgoogletest.a
> /usr/bin/cmake -P CMakeFiles/googletest.dir/cmake_clean_target.cmake
> /usr/bin/cmake -E cmake_link_script CMakeFiles/googletest.dir/link.txt --verbose=1
> /usr/bin/ar qc libgoogletest.a CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest-all.cc.o CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest_main.cc.o
> /usr/bin/ranlib libgoogletest.a
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-aarch64-linux-gnu'
> [ 17%] Built target googletest
> make  -f CMakeFiles/gtest.dir/build.make CMakeFiles/gtest.dir/depend
> make[4]: Entering directory '/<<PKGBUILDDIR>>/obj-aarch64-linux-gnu'
> cd /<<PKGBUILDDIR>>/obj-aarch64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/obj-aarch64-linux-gnu /<<PKGBUILDDIR>>/obj-aarch64-linux-gnu /<<PKGBUILDDIR>>/obj-aarch64-linux-gnu/CMakeFiles/gtest.dir/DependInfo.cmake --color=
> Scanning dependencies of target gtest
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-aarch64-linux-gnu'
> make  -f CMakeFiles/gtest.dir/build.make CMakeFiles/gtest.dir/build
> make[4]: Entering directory '/<<PKGBUILDDIR>>/obj-aarch64-linux-gnu'
> [ 20%] Building CXX object CMakeFiles/gtest.dir/test/chase_work_stealing_deque_test.cpp.o
> /usr/bin/c++ -DDEBUG -I/<<PKGBUILDDIR>>/. -isystem /usr/src/googletest/googletest -isystem /usr/src/googletest/googletest/include -fsanitize=thread -Wall -Wextra -Werror -Wno-error=cpp -std=gnu++17 -o CMakeFiles/gtest.dir/test/chase_work_stealing_deque_test.cpp.o -c /<<PKGBUILDDIR>>/test/chase_work_stealing_deque_test.cpp
> In file included from /<<PKGBUILDDIR>>/./xenium/detail/growing_circular_array.hpp:9,
>                  from /<<PKGBUILDDIR>>/./xenium/chase_work_stealing_deque.hpp:12,
>                  from /<<PKGBUILDDIR>>/test/chase_work_stealing_deque_test.cpp:1:
> /<<PKGBUILDDIR>>/./xenium/utils.hpp:80:4: error: #error "Unsupported compiler"
>    80 |   #error "Unsupported compiler"
>       |    ^~~~~
> In file included from /<<PKGBUILDDIR>>/./xenium/detail/growing_circular_array.hpp:9,
>                  from /<<PKGBUILDDIR>>/./xenium/chase_work_stealing_deque.hpp:12,
>                  from /<<PKGBUILDDIR>>/test/chase_work_stealing_deque_test.cpp:1:
> /<<PKGBUILDDIR>>/./xenium/utils.hpp: In function ‘uint64_t xenium::utils::random()’:
> /<<PKGBUILDDIR>>/./xenium/utils.hpp:84:12: error: ‘getticks’ was not declared in this scope
>    84 |     return getticks() >> 4;
>       |            ^~~~~~~~
> make[4]: *** [CMakeFiles/benchmark.dir/build.make:111: CMakeFiles/benchmark.dir/benchmarks/hash_map_benchmark.cpp.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/xenium_0.0.2+ds-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.