Your message dated Tue, 21 Jan 2020 09:15:32 +0100
with message-id <bb4b21e3-746b-25d4-a1bb-7a1700722...@debian.org>
and subject line Re: bug has been resolved
has caused the Debian Bug report #939974,
regarding osmo-trx FTBFS: undefined reference to symbol
'_ZN5boost6system16generic_categoryEv'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
939974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmo-trx
Version: 0.4.0-1
Severity: serious
Tags: ftbfs
osmo-trx fails to build from source in unstable and bullseye:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/osmo-trx.html
| /bin/bash ../libtool --tag=CXX --mode=link g++ -lpthread -I/usr/include/
-I/usr/include/ -I/usr/include/ -g -O2
-ffile-prefix-map=/build/1st/osmo-trx-0.4.0=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o
osmo-trx-uhd osmo_trx_uhd-osmo-trx.o ./device/uhd/libdevice.la
libtransceiver_common.la ../Transceiver52M/arch/x86/libarch.la ../GSM/libGSM.la
../CommonLibs/libcommon.la -lfftw3f -ltalloc -losmocore -ltalloc -losmoctrl
-losmogsm -losmocore -ltalloc -losmovty -losmocore -luhd
| libtool: link: g++ -I/usr/include/ -I/usr/include/ -I/usr/include/ -g -O2
-ffile-prefix-map=/build/1st/osmo-trx-0.4.0=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o
osmo-trx-uhd osmo_trx_uhd-osmo-trx.o ./device/uhd/.libs/libdevice.a
./.libs/libtransceiver_common.a ../Transceiver52M/arch/x86/.libs/libarch.a
../GSM/.libs/libGSM.a ../CommonLibs/.libs/libcommon.a -lpthread -lfftw3f
/usr/lib/x86_64-linux-gnu/libosmoctrl.so
/usr/lib/x86_64-linux-gnu/libosmogsm.so -ltalloc
/usr/lib/x86_64-linux-gnu/libosmovty.so
/usr/lib/x86_64-linux-gnu/libosmocore.so -luhd
| /usr/bin/ld: ./device/uhd/.libs/libdevice.a(UHDDevice.o): undefined reference
to symbol '_ZN5boost6system16generic_categoryEv'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_system.so.1.67.0: error
adding symbols: DSO missing from command line
| collect2: error: ld returned 1 exit status
| make[4]: *** [Makefile:641: osmo-trx-uhd] Error 1
| make[4]: Leaving directory '/build/1st/osmo-trx-0.4.0/Transceiver52M'
| make[3]: *** [Makefile:740: all-recursive] Error 1
| make[3]: Leaving directory '/build/1st/osmo-trx-0.4.0/Transceiver52M'
| make[2]: *** [Makefile:507: all-recursive] Error 1
| make[2]: Leaving directory '/build/1st/osmo-trx-0.4.0'
| make[1]: *** [Makefile:438: all] Error 2
| make[1]: Leaving directory '/build/1st/osmo-trx-0.4.0'
| dh_auto_build: make -j15 returned exit code 2
| make: *** [debian/rules:12: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
While reproducible uses pbuilder, I also see the issue locally in
sbuild.
Helmut
--- End Message ---
--- Begin Message ---
On Sat, 19 Oct 2019 09:50:57 +0200 Harald Welte <lafo...@osmocom.org> wrote:
> I can conform that the recent introduction of uhd 3.14.1.1-1 has fixed
> the FTBFS and the package is building fine again.
>
> --
> - Harald Welte <lafo...@osmocom.org> http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
> (ETSI EN 300 175-7 Ch. A6)
>
it built fine on a clean sid chroot, closing this report
G.
--- End Message ---
