Control: affects -1 systemd On Fri, 26 Jan 2024 20:10:40 +0100 Matthias Klose <doko@debian.org> wrote: > On 24.01.24 09:58, Emanuele Rocca wrote: > > 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 > > > > disabled ada, now ftbs with go. > > if you care about the Pi Zero, then please get involved upstream. > Listening to ARM guys, armv5t doesn't seem to raise any interest these days. > > Also having LLVM build failures, still targeting armv4t didn't raise any > attention to the Debian armel porters. > > So let's just say there is no man power to address issues, and probably > also lack of interest. This causes systemd to FTBFS on armel since the new upload of libatomic-14. No other architecture is affected. cc -o systemd-cryptsetup systemd-cryptsetup.p/src_cryptsetup_cryptsetup-keyfile.c.o systemd-cryptsetup.p/src_cryptsetup_cryptsetup.c.o systemd-cryptsetup.p/src_cryptsetup_cryptsetup-pkcs11.c.o systemd-cryptsetup.p/src_cryptsetup_cryptsetup-tpm2.c.o -Wl,--as-needed -Wl,--no-undefined -fstack-protector '-Wl,-rpath,$ORIGIN/src/shared:XXXXXXXXXXXXXXXX' -Wl,-rpath-link,/home/bluca/systemd/foo/src/shared -Wl,--start-group src/shared/libsystemd-shared-255.so /lib/arm-linux-gnueabi/libcryptsetup.so /usr/lib/arm-linux-gnueabi/libssl.so /usr/lib/arm-linux-gnueabi/libcrypto.so -Wl,--end-group -Wl,--fatal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common /usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: undefined reference to `libat_test_and_set_1_i2' collect2: error: ld returned 1 exit status On the Bugzilla report a patch has been linked, would it be possible to backport it, please? https://gcc.gnu.org/pipermail/gcc-patches/2024-January/644147.html -- Kind regards, Luca Boccassi
Attachment:
signature.asc
Description: This is a digitally signed message part