Bug#1061370: gcc-14 ftbfs on armel

[Matthias Klose]

Package: src:gcc-14
Version: 14-20240121-1
Severity: important
Tags: sid trixie ftbfs
X-Debbugs-CC: debia...@lists.debian.org

gcc-14 ftbfs on armel. This is a long standing, re-occurring issue
which never has been forwarded and committed by the armel ports to GCC
upstream. Please do it.

[...]
/usr/bin/ld: /<<PKGBUILDDIR>>/build/arm-linux-gnueabi/libatom
ic/.libs/libatomic.so.1: undefined reference to `libat_test_and_set_1_i2'
collect2: error: ld returned 1 exit status
arm-linux-gnueabi-gnatlink-13: error when calling
/usr/bin/arm-linux-gnueabi-gcc-13
gnatmake: *** link failed.
make[5]: *** [gcc-interface/Makefile:638: bldtools/oscons/xoscons] Error 4
make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/gcc/ada'
make[4]: *** [Makefile:117: osconstool] Error 2

[Emanuele Rocca]

Hi Matthias,

On 2024-01-23 09:01, Matthias Klose wrote:
> This is a long standing, re-occurring issue which never has been
> forwarded and committed by the armel ports to GCC upstream.

You seem to be aware of previous occurrences of this issue. Please share
the details you have available such as bug numbers, commits, and so
forth.

More in general though there have been several important issues with
armel lately, not least the fact that there is very little hardware
still supported by the kernel (essentially just the Raspberry Pi Zero
and 1 AIUI [0]). It seems to me that the time has come to seriously
consider whether supporting armel as an official port still makes sense.

[0] https://salsa.debian.org/kernel-team/linux/-/commit/b53e2d881063b060934bee3da9378da3b5b5387b