Source: purify Version: 2.0.0-4 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -std=gnu++11 -Wl,-z,relro -rdynamic > CMakeFiles/test_purify_fitsio.dir/purify_fitsio.cc.o > CMakeFiles/common_catch_main_object.dir/__/__/common_catch_main.cc.o -o > test_purify_fitsio > -Wl,-rpath,/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/cpp/purify:/usr/lib/x86_64-linux-gnu/openmpi/lib > ../purify/libpurify.so.2.0.0 /usr/lib/x86_64-linux-gnu/libfftw3_omp.so > /usr/lib/x86_64-linux-gnu/libfftw3.so -lCCfits -lcfitsio > /usr/lib/x86_64-linux-gnu/libsopt.so.3.0.1 -ltiff > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so > /usr/lib/x86_64-linux-gnu/libcasa_ms.so > /usr/lib/x86_64-linux-gnu/libcasa_measures.so > /usr/lib/x86_64-linux-gnu/libcasa_tables.so > /usr/lib/x86_64-linux-gnu/libcasa_scimath.so > /usr/lib/x86_64-linux-gnu/libcasa_scimath_f.so > /usr/lib/x86_64-linux-gnu/libcasa_casa.so -fopenmp > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data<void>::signs' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `vtable for > fmt::v6::format_error' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int > fmt::v6::internal::snprintf_float<double>(double, int, > fmt::v6::internal::float_specs, fmt::v6::internal::buffer<char>&)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::assert_fail(char const*, int, char const*)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::error_handler::on_error(char const*)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `char > fmt::v6::internal::decimal_point_impl<char>(fmt::v6::internal::locale_ref)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data<void>::zero_or_powers_of_10_32' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `char > fmt::v6::internal::thousands_sep_impl<char>(fmt::v6::internal::locale_ref)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `typeinfo > for fmt::v6::format_error' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `std::__cxx11::basic_string<char, std::char_traits<char>, > std::allocator<char> > > fmt::v6::internal::grouping_impl<char>(fmt::v6::internal::locale_ref)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int > fmt::v6::internal::format_float<long double>(long double, int, > fmt::v6::internal::float_specs, fmt::v6::internal::buffer<char>&)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int > fmt::v6::internal::snprintf_float<long double>(long double, int, > fmt::v6::internal::float_specs, fmt::v6::internal::buffer<char>&)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::format_error::~format_error()' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data<void>::hex_digits' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data<void>::digits' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int > fmt::v6::internal::format_float<double>(double, int, > fmt::v6::internal::float_specs, fmt::v6::internal::buffer<char>&)' > /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to > `fmt::v6::internal::basic_data<void>::zero_or_powers_of_10_64' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/purify_2.0.0-4_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! 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.
