Control: reassign -1 src:ubertooth 2018.12.R1-5 Control: tags -1 ftbfs On Fri, Jul 23, 2021 at 10:47:14PM +0200, Paul Gevers wrote: > Source: gcc-arm-none-eabi, ubertooth > Control: found -1 gcc-arm-none-eabi/15:10-2020-q4-major-1 > Control: found -1 ubertooth/2018.12.R1-5 > Severity: serious > Tags: sid bookworm >... > Apart from the freeze, this regression is blocking the migration of > gcc-arm-none-eabi to testing [1]. Due to the nature of this issue, I > filed this bug report against both packages. Can you please investigate > the situation and reassign the bug to the right package? >... > /usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: > bluetooth.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:34: > multiple definition of `used_channels'; > bluetooth_rxtx.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:34: > first defined here >...
This is the most common "FTBFS with gcc 10" reason, triggered by the cross compiler upgraded to gcc 10. It is also a FTBFS for ubertooth: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/ubertooth.html Not a problem for bullseye, but this will need fixing in ubertooth for bookworm. cu Adrian [1] https://gcc.gnu.org/gcc-10/porting_to.html
