Bug#1061370: gcc-14 ftbfs on armel
On Mon, 29 Jan 2024 at 16:38, Emanuele Rocca <ema@debian.org> wrote:
>
> Hi Luca,
>
> On 2024-01-29 01:33, Luca Boccassi wrote:
> > 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
>
> From the build logs at [1] it seems that a mix of GCC 13 and 14 packages
> was used, is this expected?
>
> Toolchain package versions: binutils_2.41.90.20240122-1 dpkg-dev_1.22.4 g++-13_13.2.0-10 gcc-13_13.2.0-10 libc6-dev_2.37-14 libstdc++-13-dev_13.2.0-10 libstdc++6_14-20240127-1 linux-libc-dev_6.6.13-1
>
> [1] https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=armel&ver=255.3-2&stamp=1706528229&raw=0
The package name is 'libatomic1' and it's not versioned after the GCC
major version like the rest, so it seems to be all working as
intended.
Reply to: