On Wed, Nov 09, 2022 at 09:58:22PM +0100, Paul Gevers wrote: > Source: android-platform-build-kati > Version: 10.0.0+r32+git20220314.09dfa26c4e59-3 > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > With a recent upload of android-platform-build-kati the autopkgtest of > android-platform-build-kati fails in testing when that autopkgtest is run > with the binary packages of android-platform-build-kati from unstable. It > passes when run with only packages from testing. In tabular form: > > pass fail > android-platform-build-kati > from testing > 10.0.0+r32+git20220314.09dfa26c4e59-3 > all others from testing from testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration to testing [1]. Can you > please investigate the situation and fix it? >... > g++ -c -std=c++17 -g -W -Wall -MMD -MP -O -DNOLOG -march=native -o > out/affinity.o src/affinity.cc >...
I was wondering why this works for me on the porterbox, but the autopkgtest fails on armel (and on ppc64el and riscv64). The relevant difference is likely the hardware, and the fact that -march=native is editied out during the build[1] but not patched out, so still used during the autopkgtest. cu Adrian [1] https://sources.debian.org/src/android-platform-build-kati/10.0.0%2Br32%2Bgit20220314.09dfa26c4e59-3/debian/rules/#L15
