Source: ms-gsl Severity: normal Dear Maintainer,
A new version of googletest has been uploaded and shortly thereafter I received word that ms-gsl autopkgtest has failed on arm64. See https://ci.debian.net/ data/autopkgtest/testing/arm64/m/ms-gsl/7637851/log.gz The error in that log looks like an underlinking problem (see below). But I can't understand how that is possible, since gtest itself builds and runs unit tests itself https://buildd.debian.org/status/fetch.php? pkg=googletest&arch=arm64&ver=1.10.0.20201018-1&stamp=1603081647&raw=0 My best guess is that there may be an incompatiblity between the test code built using g++8 and libgtest.a built with g++10. The previous successful autopkgtest used googletest 1.10.0-3 that was built with g++9. It used to be the case that googletest required everyone to build the gtest library from source and no libgtest.a was shipped. I'd suggest going that route to avoid problems. See https://github.com/google/googletest/blob/ master/googletest/README.md for building from sources (in /usr/src/ googletest). -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
