[Discuss-gnuradio] How to detect collision when two packets are transmitted simultaneously from two transmitters.

[Sumedha Goyal]

I have a setup of one receiver and two transmitters. I am implementing a
TDMA structure (using USRPs and GNURADIO) where only one packet is sent in
each slot. When both transmitters try to transmit in the same slot,
collision occurs. I would like to know
1. How can the receiver detect whether a collision has occurred or not?
2. What happens to the collided packets?


Regards,
Sumedha
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander) - runs from terminal, but not GRC

[Tom Rondeau]

On Thu, Nov 7, 2013 at 6:52 PM, Tom McDermott  wrote:
> Hi Tom,  thanks again for all your help.
>
> It runs from a terminal OK.
> The missing Qwt5 error comes when trying to run it from GRC.
>
> -- Tom

Ok, that's good news. It's likely that the problem is just in how you
are launching GRC that must not be getting the PYTHONPATH variable set
properly. Are you running gnuradio-companion from the terminal where
you've set the env variable? Out of years of habit, that's how I
always bring up GRC.

Tom



> 
> From: Tom Rondeau 
> To: Tom McDermott 
> Cc: "discuss-gnuradio@gnu.org" 
> Sent: Thursday, November 7, 2013 1:53 PM
> Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander)
>
> On Thu, Nov 7, 2013 at 4:37 PM, Tom McDermott 
> wrote:
>> Hi Tom,
>>
>> That fixed PyQwt.  Then did a cmake, make, sudo make install of all
>> gnuradio
>> sucessfully.
>>
>> When I try to run a flowgraph, the error in the GRC console window is:
>>
>> Traceback (most recent call last):
>>  File "/home/tom/Desktop/top_block.py", line 16, in 
>>import PyQt4.Qwt5 as Qwt
>> ImportError: No module named Qwt5
>>
>> looking at the packages *qwt*
>>
>> $ dpkg -l '*qwt*'
>> Desired=Unknown/Install/Remove/Purge/Hold
>> |
>>
>> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>> ||/ Name  Version  Architecture Description
>>
>> +++-==---=
>> ii  libqwt-dev6.0.0-1.2amd64Qt widgets library for
>> technical
>> rc  libqwt5-qt45.2.3-1  amd64Qt4 widgets library for
>> technical
>> un  libqwt5-qt4-de (no description available)
>> ii  libqwt66.0.0-1.2amd64Qt widgets library for
>> technical
>> un  libqwtplot3d-q (no description available)
>> ii  libqwtplot3d-q 0.2.7+svn191 amd643D plotting library based on
>> Qt4/
>> ii  libqwtplot3d-q 0.2.7+svn191 amd643D plotting library based on
>> Qt4/
>> un  python-qwt3d-q (no description available)
>> un  python-qwt5-qt (no description available)
>>
>>
>> -- Tom
>
> When you installed PyQWT, you should have configured it using:
>
> ./configure.py -Q ../qwt-5.2
> --module-install-path=/opt/qt/lib/python2.7/dist-packages/PyQt4/Qwt5
>
> That '--module-install-path' is where the Qwt module would be
> installed in to. So make sure that that directory structure is
> correct. Then, you have to make sure your PYTHONPATH is set correctly.
> In my instructions, I install everything into /opt/qt. I then make
> sure that the PYTHONPATH variable is appended with this directory.
> That should make sure that Python looks there first for PyQt4.Qwt5.
>
> So just verify that the Qwt Python module is installed and that
> PYTHONPATH is set in your environment.
>
>
> Tom
>
>
>
> ___
>> From: Tom Rondeau 
>> To: Tom McDermott 
>> Cc: "discuss-gnuradio@gnu.org" 
>> Sent: Thursday, November 7, 2013 12:35 PM
>>
>> Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander)
>>
>> On Thu, Nov 7, 2013 at 3:31 PM, Tom McDermott 
>> wrote:
>>> Hi Tom - OK, that got PyQt to install...
>>>
>>> Now install of PyQwt fails:
>>>
>>> ./configure.py -Q ../qwt-5.2
>>> --module-install-path=/opt/qt/lib/python2.7/dist-packages/PyQt4/Qwt5
>>>
>>> produces
>>>
>>> sip: Deprecation warning: ../sip/qwt5qt4/QwtModule.sip:32: %Module
>>> version
>>> number should be specified using the 'version' argument
>>> sip: Unable to find file "QtCore/QtCoremod.sip"
>>> SIP failed to generate the C++ code.
>>>
>>> -- Tpm
>>
>> Ah, ok. This is why we have to install PyQT ourselves and can't rely
>> on the Ubuntu-installed code. That QtCoremod.sip file is installed
>> when we install PyQT. My guess is that you have to set up the
>> environmental variables before trying to configure PyQWT. I updated
>> the webpage to do this before anything else, so go and look at the new
>> order of instructions and see if that helps.
>>
>> I think I did this myself and then wrote up the description out of
>> order because I thought it made more logical sense. Hopefully this
>> does it for you.
>>
>>
>> Tom
>>
>>
>>> 
>>> From: Tom Rondeau 
>>> To: Tom McDermott 
>>> Cc: GNURadio Discussion List 
>>> Sent: Thursday, November 7, 2013 12:11 PM
>>> Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander)
>>>
>>> On Thu, Nov 7, 2013 at 3:07 PM, Tom Rondeau  wrote:
 On Thu, Nov 7, 2013 at 3:01 PM, Tom McDermott 
 wrote:
> Hi Tom,  thanks for your effort.
>
> At the step where PyQt 4.10.3 is installed,
>
> python configure.py -b /opt/qt/bin -d
> /opt/qt/lib/python2.7/dist-packages
> -v
> /opt/qt/share/sip
>
>
> The command does many steps then errors out with:
> sh: 1: /usr/bin/sip: not found
> Error: Una

Re: [Discuss-gnuradio] python import error

[Tom Rondeau]

On Fri, Nov 8, 2013 at 9:26 AM, nesimi eldarov  wrote:
> Dear all,
>
> I have a very old problem. I hope someone can help me:
>
> system: Ubuntu 13.04
>
> I installed :
> python 2.7.4 version by default
> and
> sudo apt-get install gnuradio
> -
>
> I run this:
>
> $ python -c 'from gnuradio import ftw'
>
> returns this error:
>
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: cannot import name ftw
> --
> I cannot import only this one. The all others are okay.
> Do you know how to fix it?
>
> --
> nesimi eldarov


What are you trying to get with 'ftw'? That's not a GNU Radio component.

Tom

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander) - runs from terminal, but not GRC

[Marcus Leech]

Or set your PYTHONPATH in your .bashrc, and export it.
 
on Nov 08, 2013, Tom Rondeau  wrote:
On Thu, Nov 7, 2013 at 6:52 PM, Tom McDermott  wrote:> Hi Tom, thanks again for all your help.>> It runs from a terminal OK.> The missing Qwt5 error comes when trying to run it from GRC.>> -- TomOk, that's good news. It's likely that the problem is just in how youare launching GRC that must not be getting the PYTHONPATH variable setproperly. Are you running gnuradio-companion from the terminal whereyou've set the env variable? Out of years of habit, that's how Ialways bring up GRC.Tom> > From: Tom Rondeau > To: Tom McDermott > Cc: "discuss-gnuradio@gnu.org" > Sent: Thursday, November 7, 2013 1:53 PM> Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander)>> On Thu, Nov 7, 2013 at 4:37 PM, Tom McDermott > wrote:>> Hi Tom, That fixed PyQwt. Then did a cmake, make, sudo make install of all>> gnuradio>> sucessfully. When I try to run a flowgraph, the error in the GRC console window is: Traceback (most recent call last):>> File "/home/tom/Desktop/top_block.py", line 16, in >> import PyQt4.Qwt5 as Qwt>> ImportError: No module named Qwt5 looking at the packages *qwt* $ dpkg -l '*qwt*'>> Desired=Unknown/Install/Remove/Purge/Hold>> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)>> ||/ Name Version Architecture Description +++-==---=>> ii libqwt-dev 6.0.0-1.2 amd64 Qt widgets library for>> technical>> rc libqwt5-qt4 5.2.3-1 amd64 Qt4 widgets library for>> technical>> un libqwt5-qt4-de  (no description available)>> ii libqwt6 6.0.0-1.2 amd64 Qt widgets library for>> technical>> un libqwtplot3d-q  (no description available)>> ii libqwtplot3d-q 0.2.7+svn191 amd64 3D plotting library based on>> Qt4/>> ii libqwtplot3d-q 0.2.7+svn191 amd64 3D plotting library based on>> Qt4/>> un python-qwt3d-q  (no description available)>> un python-qwt5-qt  (no description available)>> -- Tom>> When you installed PyQWT, you should have configured it using:>> ./configure.py -Q ../qwt-5.2> --module-install-path=/opt/qt/lib/python2.7/dist-packages/PyQt4/Qwt5>> That '--module-install-path' is where the Qwt module would be> installed in to. So make sure that that directory structure is> correct. Then, you have to make sure your PYTHONPATH is set correctly.> In my instructions, I install everything into /opt/qt. I then make> sure that the PYTHONPATH variable is appended with this directory.> That should make sure that Python looks there first for PyQt4.Qwt5.>> So just verify that the Qwt Python module is installed and that> PYTHONPATH is set in your environment.>>> Tom ___>> From: Tom Rondeau >> To: Tom McDermott >> Cc: "discuss-gnuradio@gnu.org" >> Sent: Thursday, November 7, 2013 12:35 PM Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander) On Thu, Nov 7, 2013 at 3:31 PM, Tom McDermott >> wrote:>>> Hi Tom - OK, that got PyQt to install...>> Now install of PyQwt fails:>> ./configure.py -Q ../qwt-5.2>>> --module-install-path=/opt/qt/lib/python2.7/dist-packages/PyQt4/Qwt5>> produces>> sip: Deprecation warning: ../sip/qwt5qt4/QwtModule.sip:32: %Module>>> version>>> number should be specified using the 'version' argument>>> sip: Unable to find file "QtCore/QtCoremod.sip">>> SIP failed to generate the C++ code.>> -- Tpm Ah, ok. This is why we have to install PyQT ourselves and can't rely>> on the Ubuntu-installed code. That QtCoremod.sip file is installed>> when we install PyQT. My guess is that you have to set up the>> environmental variables before trying to configure PyQWT. I updated>> the webpage to do this before anything else, so go and look at the new>> order of instructions and see if that helps. I think I did this myself and then wrote up the description out of>> order because I thought it made more logical sense. Hopefully this>> does it for you.>> Tom>>> >>> From: Tom Rondeau >> Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander)>> On Thu, Nov 7, 2013 at 3:07 PM, Tom Rondeau  wrote: On Thu, Nov 7, 2013 at 3:01 PM, Tom McDermott  wrote:> Hi Tom, thanks for your effort.>> At the step where PyQt 4.10.3 is installed,>> python configure.py -b /opt/qt/bin -d> /opt/qt/lib/python2.7/dist-packages> -v> /opt/qt/share/sip>

Re: [Discuss-gnuradio] How to detect collision when two packets are transmitted simultaneously from two transmitters.

[Aditya Dhananjay]

Hi Sumedha,

1. You could perhaps look at the average power received over that time
slot. If there is a collision, the receive power would ostensibly be higher.

2. Traditionally, a collision implied that nothing could be done, and the
data was lost (unless one transmitter overwhelmed the other transmitter's
signal, leading to the capture effect). However over the past couple of
years, there have been techniques developed to recover packets from
collisions. You could read the "Zig-Zag decoding" paper by Shyamnath
Gollakota and Dina Katabi from SIGCOMM 2008.

http://groups.csail.mit.edu/netmit/wordpress/wp-content/themes/netmit/papers/ZigZag.pdf

Aditya



On Fri, Nov 8, 2013 at 8:44 AM, Sumedha Goyal  wrote:

> I have a setup of one receiver and two transmitters. I am implementing a
> TDMA structure (using USRPs and GNURADIO) where only one packet is sent in
> each slot. When both transmitters try to transmit in the same slot,
> collision occurs. I would like to know
> 1. How can the receiver detect whether a collision has occurred or not?
> 2. What happens to the collided packets?
>
>
> Regards,
> Sumedha
>
> ___
> 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

Re: [Discuss-gnuradio] python import error

[nesimi eldarov]

>> $ python -c 'from gnuradio import ftw'
>>
>> returns this error:
>>
>> Traceback (most recent call last):
>>   File "", line 1, in 
>> ImportError: cannot import name ftw
>> --
>> I cannot import only this one. The all others are okay.
>> Do you know how to fix it?
>>
>> --
>> nesimi eldarov
>
>
>What are you trying to get with 'ftw'? That's not a GNU Radio component.
>
>Tom
Hi Tom,

I see, therefore it does not import. There is a project:
https://www.cgran.org/wiki/ftw80211ofdmtx
It installs FTW packages into gnuradio during installation. However it does not 
import. 

did gnuradio version 3.2 had FTW?

-- 
nesimi eldarov
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] python import error

[nesimi eldarov]

 Dear all,

I have a very old problem. I hope someone can help me:

system: Ubuntu 13.04

I installed :
python 2.7.4 version by default
and
sudo apt-get install gnuradio
-

I run this:

$ python -c 'from gnuradio import ftw' 

returns this error:

Traceback (most recent call last):
  File "", line 1, in 
ImportError: cannot import name ftw
--
I cannot import only this one. The all others are okay.
Do you know how to fix it?

-- 
nesimi eldarov___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] python import error

[Tom Rondeau]

On Fri, Nov 8, 2013 at 9:57 AM, nesimi eldarov  wrote:
>
>> $ python -c 'from gnuradio import ftw'
>>
>> returns this error:
>>
>> Traceback (most recent call last):
>> File "", line 1, in 
>> ImportError: cannot import name ftw
>>
>> --
>> I cannot import only this one. The all others are okay.
>> Do you know how to fix it?
>>
>> --
>> nesimi eldarov
>
>
> What are you trying to get with 'ftw'? That's not a GNU Radio component.
>
> Tom
>
> Hi Tom,
>
> I see, therefore it does not import. There is a project:
> https://www.cgran.org/wiki/ftw80211ofdmtx
> It installs FTW packages into gnuradio during installation. However it does
> not import.
>
> did gnuradio version 3.2 had FTW?
>
> --
> nesimi eldarov

This is an OOT module that was built for version 3.2.2. If you are
using a newer version of GNU Radio, it's unlikely that it will work
out of the box. You would have to modify the ftw code to build against
your version of GNU Radio and install it or it will not work.

Tom

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] python import error

[nesimi eldarov]

>>
>> What are you trying to get with 'ftw'? That's not a GNU Radio component.
>>
>> Tom
>>
>> Hi Tom,
>>
>> I see, therefore it does not import. There is a project:
>>  https://www.cgran.org/wiki/ftw80211ofdmtx
>> It installs FTW packages into gnuradio during installation. However it does
>> not import.
>>
>> did gnuradio version 3.2 had FTW?
>>
>> --
>> nesimi eldarov
>
>This is an OOT module that was built for version 3.2.2. If you are
>using a newer version of GNU Radio, it's unlikely that it will work
>out of the box. You would have to modify the ftw code to build against
>your version of GNU Radio and install it or it will not work.
>
>Tom

I installed 3.2.2 version also into Ubuntu 9.04, but did not work.
It is really interesting how it did work before.

-- 
nesimi eldarov
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander) - runs from terminal, but not GRC

[Tom McDermott]

Hi Tom,
 
It runs under GRC when GRC is launched from a terminal but not when launched 
from the desktop. So it's not getting the modified PYTHONPATH from 
gnome-session. Looked for gnuradio-companion.desktop file to place a 
PYTHONPATH, but couldn't find it.
 
Ultimately added ppa:borg/ppa to the PPA list and pulled the latest build from 
there. That of course resolves all cases.
 
Many thanks for your considerable help on this!  Ubuntu 13.04 seems to be gone 
from the Canonical site, so 13.10 was the only practical solution at this time.
 
-- Tom
 


 From: Tom Rondeau 
To: Tom McDermott  
Cc: "discuss-gnuradio@gnu.org"  
Sent: Friday, November 8, 2013 5:56 AM
Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander) - runs from 
terminal, but not GRC
  

On Thu, Nov 7, 2013 at 6:52 PM, Tom McDermott  wrote:
> Hi Tom,  thanks again for all your help.
>
> It runs from a terminal OK.
> The missing Qwt5 error comes when trying to run it from GRC.
>
> -- Tom

Ok, that's good news. It's likely that the problem is just in how you
are launching GRC that must not be getting the PYTHONPATH variable set
properly. Are you running gnuradio-companion from the terminal where
you've set the env variable? Out of years of habit, that's how I
always bring up GRC.

Tom



> 
> From: Tom Rondeau 
> To: Tom McDermott 
> Cc: "discuss-gnuradio@gnu.org" 
> Sent: Thursday, November 7, 2013 1:53 PM
> Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander)
>
> On Thu, Nov 7, 2013 at 4:37 PM, Tom McDermott 
> wrote:
>> Hi Tom,
>>
>> That fixed PyQwt.  Then did a cmake, make, sudo make install of all
>> gnuradio
>> sucessfully.
>>
>> When I try to run a flowgraph, the error in the GRC console window is:
>>
>> Traceback (most recent call last):
>>  File "/home/tom/Desktop/top_block.py", line 16, in 
>>    import PyQt4.Qwt5 as Qwt
>> ImportError: No module named Qwt5
>>
>> looking at the packages *qwt*
>>
>> $ dpkg -l '*qwt*'
>> Desired=Unknown/Install/Remove/Purge/Hold
>> |
>>
>> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>> ||/ Name          Version      Architecture Description
>>
>> +++-==---=
>> ii  libqwt-dev    6.0.0-1.2    amd64        Qt widgets library for
>> technical
>> rc  libqwt5-qt4    5.2.3-1      amd64        Qt4 widgets library for
>> technical
>> un  libqwt5-qt4-de                     (no description available)
>> ii  libqwt6        6.0.0-1.2    amd64        Qt widgets library for
>> technical
>> un  libqwtplot3d-q                     (no description available)
>> ii  libqwtplot3d-q 0.2.7+svn191 amd64        3D plotting library based on
>> Qt4/
>> ii  libqwtplot3d-q 0.2.7+svn191 amd64        3D plotting library based on
>> Qt4/
>> un  python-qwt3d-q                     (no description available)
>> un  python-qwt5-qt                     (no description available)
>>
>>
>> -- Tom
>
> When you installed PyQWT, you should have configured it using:
>
> ./configure.py -Q ../qwt-5.2
> --module-install-path=/opt/qt/lib/python2.7/dist-packages/PyQt4/Qwt5
>
> That '--module-install-path' is where the Qwt module would be
> installed in to. So make sure that that directory structure is
> correct. Then, you have to make sure your PYTHONPATH is set correctly.
> In my instructions, I install everything into /opt/qt. I then make
> sure that the PYTHONPATH variable is appended with this directory.
> That should make sure that Python looks there first for PyQt4.Qwt5.
>
> So just verify that the Qwt Python module is installed and that
> PYTHONPATH is set in your environment.
>
>
> Tom
>
>
>
> ___
>> From: Tom Rondeau 
>> To: Tom McDermott 
>> Cc: "discuss-gnuradio@gnu.org" 
>> Sent: Thursday, November 7, 2013 12:35 PM
>>
>> Subject: Re: [Discuss-gnuradio] Ubuntu 13.10 (Saucy Salamander)
>>
>> On Thu, Nov 7, 2013 at 3:31 PM, Tom McDermott 
>> wrote:
>>> Hi Tom - OK, that got PyQt to install...
>>>
>>> Now install of PyQwt fails:
>>>
>>> ./configure.py -Q ../qwt-5.2
>>> --module-install-path=/opt/qt/lib/python2.7/dist-packages/PyQt4/Qwt5
>>>
>>> produces
>>>
>>> sip: Deprecation warning: ../sip/qwt5qt4/QwtModule.sip:32: %Module
>>> version
>>> number should be specified using the 'version' argument
>>> sip: Unable to find file "QtCore/QtCoremod.sip"
>>> SIP failed to generate the C++ code.
>>>
>>> -- Tpm
>>
>> Ah, ok. This is why we have to install PyQT ourselves and can't rely
>> on the Ubuntu-installed code. That QtCoremod.sip file is installed
>> when we install PyQT. My guess is that you have to set up the
>> environmental variables before trying to configure PyQWT. I updated
>> the webpage to do this before anything else, so go and look at the new
>> order of instructions and see if that helps.
>>
>> I think I did this myself and then wrote up the description out of

Re: [Discuss-gnuradio] GRCon '13 Hackfest Wrap-Up

[Tom Rondeau]

On Sat, Oct 5, 2013 at 8:53 AM, Martin Braun (CEL)  wrote:
> Hi everyone,
>
> following GRCon '13, we had a one-day hackfest. A *lot* of people stayed
> around for this, improving GNU Radio on all fronts.
>
> Since there has been a request to know what we did, I have started a
> wiki page:
>
> http://gnuradio.org/redmine/projects/gnuradio/wiki/Hackfest1310
>
> I would like to invite all participants to add a quick note on what was
> done. Thank you!
>
> MB

Just wanted to let everyone know that I've updated the hackfest wiki
with the work we did on burst modems that was just merged into our
master branch and will be a part of 3.7.2.

Tom

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Status of GNU Radio with OSX 10.9

[Michael Dickens]

I just pushed < https://trac.macports.org/changeset/113092 >, which allows 
exactly what you wrote there Carles: just the C++ API and runtime.  No SWIG 
Python or GRC.  Python is used during the build, but not used for runtime.  It 
should be live by ~1:30 PM/US/ET.  I'm love to hear feedback from anyone trying 
to use GNU Radio on 10.9 via MacPorts. - MLD

On Nov 7, 2013, at 4:44 PM, Carles Fernandez  wrote:
> thanks so much for your efforts and for keeping us updated on your progress. 
> I'm some steps behind of you but reproducing the path the best I can. I 
> successfully built GNU Radio runtime, pmt, blocks, fft, filter, uhd, fec, 
> trellis, analog, and volk libraries with 10.9's clang and libc++, which is 
> enough for my C++ application. Any one else would be interested in a 
> 'gnuradio-devel-mavericks' port with the libraries that compile well by now?
--

Michael Dickens, Mac OS X Programmer

Ettus Research Technical Support

Email: supp...@ettus.com

Web: http://www.ettus.com
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Status of GNU Radio with OSX 10.9

[Michael Dickens]

One further update: I played around with the SWIG provided includes for std, 
and it seems possible to tweak them to allow GNU Radio to be fully usable on 
10.9.  It's something that needs to come from upstream (the SWIG folks), since 
they need to "#ifdef CXX11" or something around the code.  But, it works with 
only a minor change to gnuradio.i which is fully backwards compatible.  I 
probably won't get back to this before Monday (busy weekend), but I wanted to 
extend the hope to others of using GRC with OSX 10.9. - MLD

On Nov 8, 2013, at 1:02 PM, Michael Dickens  wrote:
> I just pushed < https://trac.macports.org/changeset/113092 >, which allows 
> exactly what you wrote there Carles: just the C++ API and runtime.  No SWIG 
> Python or GRC.  Python is used during the build, but not used for runtime.  
> It should be live by ~1:30 PM/US/ET.  I'm love to hear feedback from anyone 
> trying to use GNU Radio on 10.9 via MacPorts.
--

Michael Dickens, Mac OS X Programmer

Ettus Research Technical Support

Email: supp...@ettus.com

Web: http://www.ettus.com


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio