[Debian-on-mobile-maintainers] Bug#983975: axc: ftbfs with GCC-11

Matthias Klose doko at debian.org
Wed Mar 3 16:10:29 GMT 2021


Package: src:axc
Version: 0.3.3-1
Severity: normal
Tags: sid bookworm
User: debian-gcc at lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/axc_0.3.3-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
[       OK ] test_db_create_should_create_necessary_tables
[ RUN      ] test_db_destroy_should_drop_all_tables
[       OK ] test_db_destroy_should_drop_all_tables
[ RUN      ] test_db_property_set_should_set_property_correctly
[       OK ] test_db_property_set_should_set_property_correctly
[ RUN      ] test_db_property_get_should_get_correctly
[       OK ] test_db_property_get_should_get_correctly
[ RUN      ] test_db_property_get_should_fail_on_no_results
[       OK ] test_db_property_get_should_fail_on_no_results
[ RUN      ] test_db_init_status_set_should_work
[       OK ] test_db_init_status_set_should_work
[ RUN      ] test_db_init_status_get_should_work
[       OK ] test_db_init_status_get_should_work
[ RUN      ] test_db_session_store_should_work
[       OK ] test_db_session_store_should_work
[ RUN      ] test_db_session_load_should_find_session
[       OK ] test_db_session_load_should_find_session
[ RUN      ] test_db_session_load_should_not_find_session
[       OK ] test_db_session_load_should_not_find_session
[ RUN      ] test_db_session_get_sub_device_sessions_should_find_and_return_correct_number
[       OK ] test_db_session_get_sub_device_sessions_should_find_and_return_correct_number
[ RUN      ] test_db_session_contains_should_return_correct_values
[       OK ] test_db_session_contains_should_return_correct_values
[ RUN      ] test_db_session_delete_should_return_correct_values
[       OK ] test_db_session_delete_should_return_correct_values
[ RUN      ] test_db_session_delete_all_should_return_correct_values
[       OK ] test_db_session_delete_all_should_return_correct_values
[ RUN      ] test_db_pre_key_store_should_work
[       OK ] test_db_pre_key_store_should_work
[ RUN      ] test_db_pre_key_store_list
[       OK ] test_db_pre_key_store_list
[ RUN      ] test_db_pre_key_get_list
[       OK ] test_db_pre_key_get_list
[ RUN      ] test_db_pre_key_load_should_return_correct_values_and_key
[       OK ] test_db_pre_key_load_should_return_correct_values_and_key
[ RUN      ] test_db_pre_key_contains_should_return_correct_values
[       OK ] test_db_pre_key_contains_should_return_correct_values
[ RUN      ] test_db_pre_key_remove
[       OK ] test_db_pre_key_remove
[ RUN      ] test_db_pre_key_get_max_id
[       OK ] test_db_pre_key_get_max_id
[ RUN      ] test_db_signed_pre_key_store_should_work
[       OK ] test_db_signed_pre_key_store_should_work
[ RUN      ] test_db_signed_pre_key_load_should_return_correct_values_and_key
[       OK ] test_db_signed_pre_key_load_should_return_correct_values_and_key
[ RUN      ] test_db_signed_pre_key_contains_should_return_correct_values
[       OK ] test_db_signed_pre_key_contains_should_return_correct_values
[ RUN      ] test_db_signed_pre_key_remove
[       OK ] test_db_signed_pre_key_remove
[ RUN      ] test_db_identity_set_local_registration_id
[       OK ] test_db_identity_set_local_registration_id
[ RUN      ] test_db_identity_get_local_registration_id
[       OK ] test_db_identity_get_local_registration_id
[ RUN      ] test_db_identity_set_and_get_key_pair
[       OK ] test_db_identity_set_and_get_key_pair
[ RUN      ] test_db_identity_save
[       OK ] test_db_identity_save
[ RUN      ] test_db_identity_get_key_pair_keys_not_found
[       OK ] test_db_identity_get_key_pair_keys_not_found
[==========] 36 test(s) run.
[  PASSED  ] 36 test(s).
mv *.g* test
mv: cannot stat '*.g*': No such file or directory
make[2]: *** [Makefile:120: test_store] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: error: make -j4 test -j1 returned exit code 2
make[1]: *** [debian/rules:25: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:10: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



More information about the Debian-on-mobile-maintainers mailing list