Bug#990240: soapyosmo: does not link with boost chrono
On Mon, Jul 05, 2021 at 12:34:04PM +0200, Christoph Berg wrote: > Re: tony mancill > > However, the patched build alone does not resolve the crash of > > sdrangelove on my system until I also install the updated hamlib4 from > > experimental. That is, sdrangelove appears to be affected by > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980472. > > > > I'm not sure what the plans are for the hamlib4 with respect to > > Bullseye. > > 4.0 is probably not the ideal version to have in bullseye, but it's a > great improvement over the version we had before (which was missing > support for many transceivers on the market today). > > Hamlib 4.1 is unfortunately incompatible with 4.0 in some internal > data structures (which are supposed to be opaque, but aren't always in > practise), so updating to that would need fixes in other programs (I > know about wsjtx, see libhamlib4's Breaks:). I don't think we can or > should try to push that into bullseye. Yes, wstjx is twice as popular as sdrangelove according to popcon, and I am surprised the delta isn't even greater. > > Any concerns with an upload of soapyosmo to get us one step > > closer? > > Seems sensible to me. Thank you for the response. I will to upload with this (minimal) change and request an unblock. Given that the upload addresses the retitled bug in soapysdr, I will include "Closes: #990240" but want to point out that the "affects" for sdrangelove isn't really applicable. As far as I can tell, the "ERROR" logged during startup isn't the actual cause of the crash, it simply happens to be the last thing logged before the crash. > [ERROR] > SoapySDR::loadModule(/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/librfspaceSupport.so) > dlopen() failed: > /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/librfspaceSupport.so: undefined > symbol: _ZN5boost6chrono12steady_clock3nowEv > Hash collision!!! Fatal error!! > pure virtual method called Cheers, tony signature.asc Description: PGP signature
Bug#990240: soapyosmo: does not link with boost chrono
> Fwiw, sdrangelove itself is quite obsolete and afaict hasn't seen any > updates for years. The successor is sdrangel which I'm trying to > package, but haven't finished reviewing the copyrights yet. Apart from > that, the package is ready: > > https://salsa.debian.org/debian-hamradio-team/sdrangel I would love to see sdrangel in debian! Christoph, How many beers do I owe you? :D
Bug#990240: soapyosmo: does not link with boost chrono
Re: tony mancill > However, the patched build alone does not resolve the crash of > sdrangelove on my system until I also install the updated hamlib4 from > experimental. That is, sdrangelove appears to be affected by > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980472. > > I'm not sure what the plans are for the hamlib4 with respect to > Bullseye. 4.0 is probably not the ideal version to have in bullseye, but it's a great improvement over the version we had before (which was missing support for many transceivers on the market today). Hamlib 4.1 is unfortunately incompatible with 4.0 in some internal data structures (which are supposed to be opaque, but aren't always in practise), so updating to that would need fixes in other programs (I know about wsjtx, see libhamlib4's Breaks:). I don't think we can or should try to push that into bullseye. > Any concerns with an upload of soapyosmo to get us one step > closer? Seems sensible to me. Fwiw, sdrangelove itself is quite obsolete and afaict hasn't seen any updates for years. The successor is sdrangel which I'm trying to package, but haven't finished reviewing the copyrights yet. Apart from that, the package is ready: https://salsa.debian.org/debian-hamradio-team/sdrangel Christoph
Bug#990240: soapyosmo: does not link with boost chrono
On Wed, Jun 23, 2021 at 08:50:13PM +0200, Sebastian Ramacher wrote: > Indeed, soapyosmo does not link with boost chrono. Reassigning > accordingly. The attached patch updates the build to link against boost chrono. However, the patched build alone does not resolve the crash of sdrangelove on my system until I also install the updated hamlib4 from experimental. That is, sdrangelove appears to be affected by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980472. I'm not sure what the plans are for the hamlib4 with respect to Bullseye. Any concerns with an upload of soapyosmo to get us one step closer? The patch/debdiff is attached. Thanks, tony diff -Nru soapyosmo-0.2.5/debian/changelog soapyosmo-0.2.5/debian/changelog --- soapyosmo-0.2.5/debian/changelog 2019-10-20 08:31:08.0 -0700 +++ soapyosmo-0.2.5/debian/changelog 2021-07-03 09:31:09.0 -0700 @@ -1,3 +1,10 @@ +soapyosmo (0.2.5-4) UNRELEASED; urgency=medium + + * Team upload. + * Add boost::chrono to build (Closes: #990240) + + -- tony mancill Sat, 03 Jul 2021 09:31:09 -0700 + soapyosmo (0.2.5-3) unstable; urgency=medium * Upload to unstable diff -Nru soapyosmo-0.2.5/debian/control soapyosmo-0.2.5/debian/control --- soapyosmo-0.2.5/debian/control 2019-10-20 08:29:52.0 -0700 +++ soapyosmo-0.2.5/debian/control 2021-07-03 09:31:09.0 -0700 @@ -7,6 +7,7 @@ debhelper (>= 12), cmake, libboost-dev, +libboost-chrono-dev, libboost-system-dev, libboost-thread-dev, libosmosdr-dev, diff -Nru soapyosmo-0.2.5/debian/patches/boost_chrono.patch soapyosmo-0.2.5/debian/patches/boost_chrono.patch --- soapyosmo-0.2.5/debian/patches/boost_chrono.patch 1969-12-31 16:00:00.0 -0800 +++ soapyosmo-0.2.5/debian/patches/boost_chrono.patch 2021-07-03 09:31:09.0 -0700 @@ -0,0 +1,10 @@ +--- a/CMakeLists.txt b/CMakeLists.txt +@@ -102,6 +102,7 @@ + SET(BOOST_REQUIRED_COMPONENTS + thread + system ++chrono + ) + + if(UNIX AND NOT BOOST_ROOT AND EXISTS "/usr/lib64") diff -Nru soapyosmo-0.2.5/debian/patches/series soapyosmo-0.2.5/debian/patches/series --- soapyosmo-0.2.5/debian/patches/series 2019-09-22 18:12:05.0 -0700 +++ soapyosmo-0.2.5/debian/patches/series 2021-07-03 09:31:09.0 -0700 @@ -1 +1,2 @@ internal-common-library +boost_chrono.patch signature.asc Description: PGP signature
