On Fri, Aug 26, 2022 at 05:23:20PM -0700, Matthew Fernandez wrote: > > > On 8/26/22 15:57, Tobias Frost wrote: > > Source: rumur > > Version: 2020.12.20-1 > > Severity: important > > > > Looking at the autopkgtest results for arm64 and armel: > > > > /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_read': > > checker.c:(.text+0x3b90): undefined reference to `__atomic_load_16' > > /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_write': > > checker.c:(.text+0x3bb8): undefined reference to `__atomic_store_16' > > /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_cas': > > checker.c:(.text+0x3bf0): undefined reference to > > `__atomic_compare_exchange_16' > > /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_cas_val': > > checker.c:(.text+0x3c2c): undefined reference to > > `__atomic_compare_exchange_16' > > > > This could be missing linking to libatomic. (Did not check if it is > > actually the case, just by looking at the symbols) > > > > I thought this was fixed in 620e514c1d322e05a9e67bb09cd0dc68cb810d38¹ that > made it into 2020.05.27-1, but it seems not. Am I expected to fix this in a > patch release to 2020.12.20-1? Because I’m also the upstream maintainer and > this package has a relatively small community of users who upgrade > frequently, I usually just roll fixes into the next upstream release. So if > this is not reproducible on the latest (2022.08.20-1) is there anything to > be done? >
With your description that the userbase is quite small, I guess that an update of the package in stable (2020.12.20-1) is not needed. https://ci.debian.net/packages/r/rumur/ tells me that this failure was still in 2022.08.20-1. > ¹ > https://github.com/Smattr/rumur/commit/620e514c1d322e05a9e67bb09cd0dc68cb810d38 ( Mmmm. I'm not sure what this patch does, frankly… ) What I see is that the test program that fails to link is not linked against latomic: + rumur --output checker.c model.m + cc -std=c11 checker.c -lpthread (from https://ci.debian.net/data/autopkgtest/unstable/arm64/r/rumur/25034806/log.gz) -- tobi
