Bug#1062354: libatomic1: 14-20240127-1 missing libat_test_and_set_1_i2
Control: severity 1061370 grave Control: forcemerge -1 1061370 Matthias Klose [2024-02-01 8:30 +0100]: > please don't file duplicate reports, see #1061370 Ah, sorry -- it wasn't clear from the title that it was about this problem, nor was it RC. Marking a duplicate, so that it's easier to find. Pitti
Bug#1062354: libatomic1: 14-20240127-1 missing libat_test_and_set_1_i2
On 01.02.24 07:36, Martin Pitt wrote: Package: libatomic1 Version: 14-20240127-1 Severity: grave Justification: breaks a lot of unrelated packages Hello, yesterday's cockpit armel build failed [1] on armel like this in the ./configure test for the PCP library: | configure:6158: gcc -o conftest -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c -lssh >&5 | /usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: undefined reference to `libat_test_and_set_1_i2' PCP hasn't changed since the previous build [2]; however, libatomic1 (via gcc-14) did -- [2] built against libatomic1/gcc 13.2.0-9. I spot-checked a few of the autopkgtest regressions on the PTS [3], and they all failed on the exact same issue, e.g. [4]. Thanks! Martin [1] https://buildd.debian.org/status/fetch.php?pkg=cockpit=armel=310-1=1706722995=0 [2] https://buildd.debian.org/status/fetch.php?pkg=cockpit=armel=309-1=1705590895=0 [3] https://tracker.debian.org/pkg/gcc-14 [4] https://ci.debian.net/packages/3/389-ds-base/testing/armel/42559327/ please don't file duplicate reports, see #1061370
Bug#1062354: libatomic1: 14-20240127-1 missing libat_test_and_set_1_i2
Package: libatomic1 Version: 14-20240127-1 Severity: grave Justification: breaks a lot of unrelated packages Hello, yesterday's cockpit armel build failed [1] on armel like this in the ./configure test for the PCP library: | configure:6158: gcc -o conftest -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c -lssh >&5 | /usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: undefined reference to `libat_test_and_set_1_i2' PCP hasn't changed since the previous build [2]; however, libatomic1 (via gcc-14) did -- [2] built against libatomic1/gcc 13.2.0-9. I spot-checked a few of the autopkgtest regressions on the PTS [3], and they all failed on the exact same issue, e.g. [4]. Thanks! Martin [1] https://buildd.debian.org/status/fetch.php?pkg=cockpit=armel=310-1=1706722995=0 [2] https://buildd.debian.org/status/fetch.php?pkg=cockpit=armel=309-1=1705590895=0 [3] https://tracker.debian.org/pkg/gcc-14 [4] https://ci.debian.net/packages/3/389-ds-base/testing/armel/42559327/
