[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1017507: vimix FTBFS on riscv64: needs to be linked with libatomic



Source: vimix
Version: 0.7.0+git20220523+ds
Severity: important
Tags: ftbfs
User: debian-riscv@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-riscv@lists.debian.org

Dear maintainer,

vimix fails to build on riscv64 architecture.

The full build log is available there:
https://buildd.debian.org/status/fetch.php?pkg=vimix&arch=riscv64&ver=0.7.0%2Bgit20220523%2Bds-2&stamp=1654605746&raw=0

| /usr/bin/ld: CMakeFiles/vimix.dir/Metronome.cpp.o: in function `asio::detail::posix_mutex::unlock()':
| /usr/include/asio/detail/posix_mutex.hpp:57: undefined reference to `__atomic_exchange_1'
| /usr/include/asio/detail/deadline_timer_service.hpp:263: undefined reference to `__atomic_exchange_1'
| /usr/bin/ld: CMakeFiles/vimix.dir/Metronome.cpp.o: in function `std::__atomic_base<bool>::exchange(bool, std::memory_order)':
| /usr/include/c++/11/bits/atomic_base.h:499: undefined reference to `__atomic_exchange_1'
| collect2: error: ld returned 1 exit status
| make[3]: *** [CMakeFiles/vimix.dir/build.make:1329: vimix] Error 1

It used to build successfully in the past as linking with -pthread
automatically links with libatomic, however the recent upload of glibc
2.34 made the -pthread flag not fully necessary anymore.

The workaround is to explicitly link with libatomic like in the attached patch. 
Could you please check and apply this patch?

Thanks
Hieu.

Attachment: fix-riscv64-fails-to-build.patch
Description: fix-riscv64-fails-to-build.patch


Reply to: