Hi Lazygranch, well, good news is that it's really just ctrlport. If you don't care about that: it's not even going to crash anything at runtime, as far as I can tell. You just won't be able to use ctrlport.
If you do care: So, ctrlport is our RPC framework, with which you can control GNU Radio as runtime from afar. In fact, it's as far as I've encountered, practically only used to read the performance counters (so, for benchmarking purposes) (might not apply to the Android port of GNU Radio). The middleware over which ctrlport works is Thrift – which we've had to find out is very terrible at being a well-packaged and reliably maintained thing. So, it's sadly possible that the GNU Radio build system found a Thrift version that looks like it would work, but that in fact doesn't. For example, doesn't contain C++ bindings. Or Python bindings. Now, I've got to admit that I've never used GR on Suse, thus it's really possible this is something triggered by the Thrift package in the Suse repos. I certainly don't blame Suse if this is Suse-specific – all distros I've looked at use terrible hacks and disable a lot of Thrift's features in the configure step to make Thrift build at all. So, given you care enough: Please tell us which version of Thrift you have. You might have one newer than we expect! And also, check your package manager for Thrift packages you have and haven't installed – I really don't know how Suse packages up thrift and its individual bindings. Best regards, Marcus On 27.03.2017 04:05, li...@lazygranch.com wrote: > Since "make test" precedes "make install" and that I had an older > version of gnuradio running, I did the "make install" with the new > build. The ctest command was run from the build directory. > > http://pastebin.com/DWjY0YQ8 > > On Sun, 26 Mar 2017 16:55:12 +0200 > Marcus Müller <marcus.muel...@ettus.com> wrote: > >> Hi nameless :) >> >> could you share the output of >> >> ctest -V -R cpp_py >> >> ctest -V -R ctrlport_probes >> >> with us? >> >> >> Regarding Boost: well, yeah, 1.54. is indeed not very recent, but >> *should* work. Same goes for the slightly dusty GCC 4.8.5; however, >> it's pretty uncommon to see a rather recent SWIG (3.0.10 in your >> case) paired with these two. So that's a bit surprising! >> >> Best regards, >> Marcus >> >> On 03/26/2017 12:16 PM, li...@lazygranch.com wrote: >>> From make test: >>> The following tests FAILED: >>> 24 - qa_cpp_py_binding (Failed) >>> 25 - qa_cpp_py_binding_set (Failed) >>> 26 - qa_ctrlport_probes (Failed) >>> >>> >>> Building for version: 3.7.12git-44-g0d5fd62c / 3.7.12git >>> Linux linux.suse 4.4.49-16-default #1 SMP Sun Feb 19 17:40:35 UTC >>> 2017 (70e9954) x86_64 x86_64 x86_64 GNU/Linux >>> >>> The output from cmake is at this pastebin >>> http://pastebin.com/W5SidSsY >>> >>> OS is opensuse 42.2. I changed the rev of thrift to 0.9.3 since some >>> threads seem to believe the old rev causes an error. >>> >>> My boost is a bit old: >>> Boost version: 1.54.0 >>> >>> I can probably upgrade to 1.61 without too much work if that helps. >>> >>> >>> >>> _______________________________________________ >>> Discuss-gnuradio mailing list >>> Discuss-gnuradio@gnu.org >>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
