[Debian-mobcom-maintainers] Bug#966890: srslte: FTBFS: ld: CMakeFiles/srslte_rf.dir/rf_soapy_imp.c.o:./obj-x86_64-linux-gnu/lib/src/phy/rf/./lib/src/phy/rf/rf_soapy_imp.c:81: multiple definition of `zero_mem'; CMakeFiles/srslte_rf.dir/rf_uhd_imp.c.o:./obj-x86_64-linux-gnu/lib/src/phy/rf/./lib/src/phy/rf/rf_uhd_imp.c:73: first defined here

Lucas Nussbaum lucas at debian.org
Mon Aug 3 09:06:45 BST 2020


Source: srslte
Version: 18.06.1-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-comment -Wno-reorder -Wno-unused-but-set-variable -Wno-unused-variable -Wformat -Wmissing-field-initializers -Wtype-limits -std=c++03 -O3 -DBUILD_TYPE_RELEASE -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -shared -Wl,-soname,libsrslte_rf.so -o libsrslte_rf.so CMakeFiles/srslte_rf.dir/rf_imp.c.o CMakeFiles/srslte_rf.dir/rf_uhd_imp.c.o CMakeFiles/srslte_rf.dir/uhd_c_api.cpp.o CMakeFiles/srslte_rf.dir/rf_blade_imp.c.o CMakeFiles/srslte_rf.dir/rf_soapy_imp.c.o  libsrslte_rf_utils.a ../libsrslte_phy.a -luhd -lbladeRF -lSoapySDR -lfftw3f -lpthread -lm 
> /usr/bin/ld: CMakeFiles/srslte_rf.dir/rf_soapy_imp.c.o:./obj-x86_64-linux-gnu/lib/src/phy/rf/./lib/src/phy/rf/rf_soapy_imp.c:81: multiple definition of `zero_mem'; CMakeFiles/srslte_rf.dir/rf_uhd_imp.c.o:./obj-x86_64-linux-gnu/lib/src/phy/rf/./lib/src/phy/rf/rf_uhd_imp.c:73: first defined here
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/srslte_18.06.1-9_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the Debian-mobcom-maintainers mailing list