Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

On 04/29/2017 06:41 PM, Cinaed Simson wrote: > The test for polar uses python-scipy which requires scipy. Actually, I don't think this is true. In Debian and Ubuntu, just about all the libraries with the python hooks are named python-. On you system it may be called scipy. In fact, that's its

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

Sure, no problem. Since you're trying to compile the latest and greatest, I assume you used the command: git clone --recursive https://github.com/gnuradio/gnuradio.git Now you have not only the latest and greatest, but also every release since October 2009. Just cd into the directory the

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

I'm afraid you are going to have to dumb it down for me. I don't see where to enter the path to the git repository. In other words git checkout v3.7.11 needs to know the location of the git source. Doing some googling, it looks like that is for a situation where the git source is local.

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

I've never bothered with thrift. Even after using GNU Radio for 3+ years, I've never used gr-ctrlport either. 3.7.11 is the latest release. But there's probably nothing particularly wrong with 3.7.12git-101-g098dc3e0. I would continue trying to work out the issues with that first. In fact,

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

I suppose I could uninstall thrift since that looks really hosed on my system. That would get rid of some errors. Is there a recommended rev?   Original Message   From: Ron Economos Sent: Saturday, April 29, 2017 7:03 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] test and

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

git checkout v3.7.11 But you're still going to have the same test failures. It's not something new. Ron On 04/29/2017 06:57 PM, li...@lazygranch.com wrote: How do I go back one rev on github? Original Message From: Cinaed Simson Sent: Saturday, April 29, 2017 6:42 PM To:

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

How do I go back one rev on github?   Original Message   From: Cinaed Simson Sent: Saturday, April 29, 2017 6:42 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0 On 04/29/2017 05:52 PM, li...@lazygranch.com wrote: > I have ZMQ.

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

On 04/29/2017 05:52 PM, li...@lazygranch.com wrote: > I have ZMQ. Here is the cmake finding it: > > -- Configuring gr-wxgui support... > -- Dependency ENABLE_GNURADIO_RUNTIME = ON > -- Dependency ENABLE_GR_FFT = ON > -- Dependency ENABLE_GR_FILTER = ON > -- Dependency ENABLE_GR_ANALOG =

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

There are additional dependencies in the test that aren't checked for in the cmake. python-scipy and python-zmq are the ones that I know about. You can find the why the tests failed in the file: install_dir/build/Testing/Temporary/LastTest.log Ron On 04/29/2017 05:52 PM, li...@lazygranch.com

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

I have ZMQ. Here is the cmake finding it: -- Configuring gr-wxgui support... -- Dependency ENABLE_GNURADIO_RUNTIME = ON -- Dependency ENABLE_GR_FFT = ON -- Dependency ENABLE_GR_FILTER = ON -- Dependency ENABLE_GR_ANALOG = ON -- Dependency ENABLE_PYTHON = ON -- Dependency NUMPY_FOUND =

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

For the polar encoder/decoder and zeromq tests, you need the following dependencies. I'm not sure about the other failures. python-scipy python-zmq Ron On 04/29/2017 11:31 AM, li...@lazygranch.com wrote: Opensuse 42.2 uname -a Linux linux-0u81 4.4.57-18.3-default #1 SMP Thu Mar 30 06:39:47

[Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

Opensuse 42.2 uname -a Linux linux-0u81 4.4.57-18.3-default #1 SMP Thu Mar 30 06:39:47 UTC 2017 (39c8557) x86_64 x86_64 x86_64 GNU/Linux --- Building for version: 3.7.12git-101-g098dc3e0 / 3.7.12git Entire cmake output at: https://pastebin.com/Gqa32538 -- Errors in the doxygen

Re: [Discuss-gnuradio] CMake error related to log4cpp in non-standard location

On the other hand, the current git pull has fixed the LOG4CPP problem I had with opensuse 42.2. http://gnuradio.4.n7.nabble.com/fail-tests-for-qa-cpp-py-binding-qa-cpp-py-binding-set-qa-ctrlport-probes-td63291.html It now works for both the local library build of log4cpp and the standard

[Discuss-gnuradio] Strange behaviour while importing oot module

Hi, I just wrote a new oot module rshfiq with gnuradio v3.7.9.1-145-g5e383b0b I get problems to load my module. Testing directly with python, I get: $ python Python 2.7.13 (default, Mar 30 2017, 12:47:27) [GCC 5.4.0] on linux2 Type "help", "copyright", "credits" or "license" for more

Re: [Discuss-gnuradio] CMake error related to log4cpp in non-standard location

Ah; thanks Bastian. I sort of remembered that something was committed that updated the use of log4cpp info. That's good. The downside is that this is not part of the current GR release, so most users won't get its benefits for a while longer -- until the next release. In MacPorts, folks can

Re: [Discuss-gnuradio] Volk functions in OOT on Mac

Hi Vamsi - Check out how this OOT modules does it, especially this commit: https://github.com/bastibl/gr-ieee802-15-4/commit/c37a45f2594e2b6f0403141e23ca12a76285b18f . - MLD On Sat, Apr 29, 2017, at 01:34 AM, vamsi krishna wrote: > Thanks for the information. I have the below fix which gets me

Re: [Discuss-gnuradio] Error building gr-burst in Ubuntu 16.04 and Volk 1.2.1

Thanks Nathan. I upgraded to Volk 1.3 with apt and, as you said, the problem was solved. El Viernes 28 de abril de 2017 17:59, "West, Nathan" escribió: This was fixed a while ago. Use VOLK version 1.2.3 or 1.3. On Fri, Apr 28, 2017 at 8:34 AM,

Re: [Discuss-gnuradio] How to tell Flowgraph to Stop in Work()?

Hi, maybe it's enough to return WORK_DONE (= -1) from work(). Best, Bastian On 04/29/2017 01:32 AM, Ghost Op wrote: > I'm working on a module in C++ and when a condition happens I want my > work function to signal to the flowgraph to stop. > > I saw some references for python to