Re: [Discuss-gnuradio] buildroot installation not generating/placing .pc files

2016-11-21 Thread Cinaed Simson
On 11/21/2016 07:23 AM, gutelfuldead wrote: > Gwen, > > One of the hold ups that I neglected to mention in this because it > wasn't a dependency for what I needed, was that buildroot was throwing > errors when compiling the gr-fec module specifically. > > I initially was building all of the nat

Re: [Discuss-gnuradio] "from gnuradio import gr" fails with a Fatal Python error

2016-11-21 Thread Michael Dickens
Glad that you are getting GR working on your Mac. If you want to make sure "which python" results in a MacPorts version, use "port select": {{{ port select --list python }}} will list the options; mine are: {{{ % port select --list python Available versions for python: none

Re: [Discuss-gnuradio] "from gnuradio import gr" fails with a Fatal Python error

2016-11-21 Thread Gilad Beeri (ApolloShield)
Hi, Seems like you got it. I'm writing here analysis and fixing steps for future generations. 1. Reproduce the problem by running 'python -c "from gnuradio import gr' - that should crash and print the error 2. Running "which python" should show the python binary used, most probably /us

Re: [Discuss-gnuradio] "from gnuradio import gr" fails with a Fatal Python error

2016-11-21 Thread Michael Dickens
Hi Gilad - IIRC this error means that Python installs are being mixed between linking and runtime. For example, linking against the macOS provided Python and then trying to use MacPorts' Python for runtime execution. If this statement doesn't help, email me off-list & we'll work through your issue.

[Discuss-gnuradio] "from gnuradio import gr" fails with a Fatal Python error

2016-11-21 Thread Gilad Beeri (ApolloShield)
Hi, The Python statement "from gnuradio import gr" crashes the Python process with "Fatal Python error: PyThreadState_Get: no current thread" (mac OS 10.12.1, GNU Radio 3.7.10.1 using Mac Ports, full log is attached). I tried following the cleanup process detailed in https://github.com/metacollin/

Re: [Discuss-gnuradio] buildroot installation not generating/placing .pc files

2016-11-21 Thread gutelfuldead
Gwen, One of the hold ups that I neglected to mention in this because it wasn't a dependency for what I needed, was that buildroot was throwing errors when compiling the gr-fec module specifically. I initially was building all of the native gnuradio packages for the platform just to have

Re: [Discuss-gnuradio] buildroot installation not generating/placing .pc files

2016-11-21 Thread gwenhael.goavec
Hello, I'm not really happy by this solution because, usually, buildroot built everything without this type of tricks... But, currently, with a fresh buildroot git I'm unable to reproduce your issue. Everything compile fine, maybe an issue with your version of buildroot. I encourage you to contri

Re: [Discuss-gnuradio] New Module using gr_modtool Error

2016-11-21 Thread Michael Dickens
Hi Vamsi - You didn't post the error, though I'm guessing it's that when you execute anything that uses your new OOT Python does not find the OOT install. Also I'm not sure where you're getting your instructions from, but you don't "sudo make" ... just "make" is plenty good enough. For a "normal"

Re: [Discuss-gnuradio] gr-ieee802-11 tx and rx

2016-11-21 Thread Bastian Bloessl
Hi, > On 21 Nov 2016, at 11:34, Nikita Airee wrote: > > I am working on the gr-ieee802-11(https://github.com/bastibl/gr-ieee802-11 > ) > > Setup consists of 2 usrp 2953R (X310) connected via SMA and 30 dB attenuator > at the Rx end. > > The problem

[Discuss-gnuradio] gr-ieee802-11 tx and rx

2016-11-21 Thread Nikita Airee
Hi everyone! I am working on the gr-ieee802-11(https://github.com/bastibl/gr-ieee802-11) Setup consists of 2 usrp 2953R (X310) connected via SMA and 30 dB attenuator at the Rx end. The problem I'm facing is that the packets that are sent do not get decoded at the reciever for high sample rates o