Hi,
On 2025-01-22 09:51, Bo YU wrote:
coot has FTBFS issues on riscv64 and mips64el due to atomic issue:
```
...
/usr/bin/ld: mini-rsr.o: in function `bool
boost::lockfree::queue<std::function<void
(int)>*>::pop<std::function<void
(int)>*>(std::function<void (int)>*&)':
/usr/include/boost/lockfree/queue.hpp:448:(.text._ZN5boost8lockfree5queueIPSt8functionIFviEEJEE3popIS5_EEbRT_[_ZN5boost8lockfree5queueIPSt8functionIFviEEJEE3popIS5_EEbRT_]+0xfa):
undefined reference to `__atomic_compare_exchange_16'
collect2: error: ld returned 1 exit status
...
```
Seehttps://buildd.debian.org/status/fetch.php?pkg=coot&arch=mips64el&ver=1.1.09%2Bdfsg-3&stamp=1736993525&raw=0
andhttps://buildd.debian.org/status/fetch.php?pkg=coot&arch=riscv64&ver=1.1.09%2Bdfsg-3&stamp=1737361754&raw=0
The workaround is to link libatomic explicitly and I have tested it on
riscv64 but no test on mips64el.
Thanks a lot for giving this a look. Am I right that I should just add
-latomic to LDFLAGS? Can I do this for all the architectures, or just is
this riscv64 and mips64el specific?
Best,
Andrius
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
