Re: [Discuss-gnuradio] GNURadio Error On Mac

Hi Vamsi - Glad to hear you worked out the issue. Cheers! - MLD On Sun, Apr 2, 2017 at 4:21 PM, Vamsi Krishna Adsumilli wrote: > Thanks for the reply. > We were able to narrow down the issue. After generating a OOT module using > gr_modtool, i have incorrectly edited the

Re: [Discuss-gnuradio] GNURadio Error On Mac

Hi Vamsi - It looks like you're doing everything correctly for building & installing your OOT & GR itself. If I had to guess, I'd think that, somehow, the 2 argument to "map" is being provided either directly or indirectly in the "top_block.py" script & clearly doesn't support iteration & needs

Re: [Discuss-gnuradio] OS X Fuzzy Text in GRC

Can you send me (off list) a screen snapshot or the like so that I can see what you mean by "fuzzy"? I see nothing out of the ordinary in GRC when running, but then maybe I'm not looking at the correct text... Cheers! - MLD On Sun, Apr 2, 2017, at 10:12 AM, Dave NotTelling wrote: > I just

[Discuss-gnuradio] tests for ctrlport on macOS?

I recently had a MacPorts ticket to enable +ctrlport. After updating thrift to 0.10.0, along with a patch to fix gr-fec's possible use of c++11's 'constexpr', I got GR to build with ctrlport enabled. Ticket fixed, since the issue was in MacPorts. Running "make test" results in failures in the

Re: [Discuss-gnuradio] gr-fec: why BOOST_CONSTEXPR_OR_CONST?

Thanks for the feedback. PR is https://github.com/gnuradio/gnuradio/pull/1221 . - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] gr-fec: why BOOST_CONSTEXPR_OR_CONST?

I have a MacPorts ticket requesting that I enable CTRLPORT, which requires Thrift, which was recently updated to 0.10.0 in MacPorts -- so I thought it worth a try again to see if it works. Thrift requires C++11 for building, which means that "gnuradio +ctrlport" will also require C++11. Easy

Re: [Discuss-gnuradio] gnuradio-companion swig error?

I don't know why your post didn't go through. The gr-osmosdr port contents look correct. Your script works for me on my OS X box (admittedly, 10.12 latest). Let's take the discussion on-list, and I'll help you debug this & if there's something relevant I'll reply back to the GR list. -

Re: [Discuss-gnuradio] gnuradio-companion swig error?

According to nabble, your original post has yet to be authorized. I'll append it for completion. So you're running on an older OS X box (10.8), using the libc++ hack for older systems. That should be OK. Most folks I know who use it do it with 10.6 or 10.7, but it should work on 10.8 too. If you

Re: [Discuss-gnuradio] volk compile error on raspberry pi3

Hi Cinaed - Check out < https://brmlab.cz/user/jenda/rpi-gcc >. - MLD On Mon, Feb 20, 2017, at 03:36 PM, Cinaed Simson wrote: > Any know if the following bug has been resolved? > > It appears this bug has existed since the first pi was released. > > Anyone know if a patch exists? > > I did

Re: [Discuss-gnuradio] Runtime error on Mac OSX 10.7

Hi Matthew - Hmm ... well, testing on 10.7 will be tricky for debugging purposes. It looks like you installed GR via MacPorts ... yes? This looks like the same issue as < https://trac.macports.org/ticket/53236[1] >, yes? OK; I'm working on fixing this; hopefully this afternoon. Cheers! - MLD On

Re: [Discuss-gnuradio] OS X Sierra complete build

Hi Greg - What usually works is the following: {{{ sudo port clean doxygen sudo port install doxygen sudo port clean gnuradio sudo port install gnuradio }}} If that fails, email me off-list & I'll help debug. - MLD On Tue, Dec 6, 2016, at 01:43 PM, Gregory Ratcliff wrote: > Just

Re: [Discuss-gnuradio] OS X Sierra complete build

Hi Greg - what usually works is the following: {{{ sudo port clean doxygen sudo port install doxygen sudo port clean gnuradio sudo port install gnuradio }}} If that fails, email me off-list & I'll help debug. - MLD > On Dec 6, 2016, at 7:08 AM, Gregory Ratcliff wrote: > > Just

Re: [Discuss-gnuradio] macOS Sierra advice/recommendations (N210 + HackRF )

Hi Greg - Good to hear from another OS X GR user! I think 1-3 in your list are pretty accurate; I'll add for 3 that it's easy to use MacPorts to do development with GR, either directly inside MP or via OOT modules. I'll add 4: from source! I use a mix of 3 and 4, which with the proper CMake

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

Hi Vamsi - I'm glad that fixed the issue for you. The crash happens because the OOT is being linked to a specific ABI (e.g., MacPorts Python library), while the runtime is trying to use a different API (system Python library). The libraries' ABIs are different enough to confuse Apple's dynamic

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

ython" symlink, so it can be fixed by either > using "python2.7" (which exists in /opt/local/bin and will be used > before the system's binary) or by creating a symlink with "ln -s > /usr/local/bin/python2.7 /usr/local/bin/python". After symlinking, > 'p

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

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

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

need to set all of the PYTHON variables accordingly. Hope this is useful! - MLD On Mon, Nov 21, 2016, at 08:13 AM, Michael Dickens wrote: > > -- Forwarded message -- > From: *vamsi krishna* <vamsi...@yahoo.com> > Date: Sun, Nov 20, 2016 at 11:09 PM > Subject: Re: [

Re: [Discuss-gnuradio] Linking gr-digital in OOT Module (Success on OSX, fails on Linux)

The lib/ and swig/ libraries used inside cmake are generally the same. I'll be very curious how this issue pans out! Cheers! - MLD On Thu, Nov 17, 2016, at 08:13 AM, Garver, Paul W wrote: > I’m thinking I should write a simple C++ harness to call the block. > That way, I can isolate a SWIG

Re: [Discuss-gnuradio] Linking gr-digital in OOT Module (Success on OSX, fails on Linux)

Hi Paul - You are correct that adding "DIGITAL" as you write should add that component in for headers and library linking. Did you clean the build directory after changing this setting? Sometimes CMake won't redo the linkage internally, and one just has to "rm -rf" the whole build directory and

Re: [Discuss-gnuradio] run gnuradio on mac

On Fri, Oct 21, 2016, at 11:25 PM, w xd wrote: > I have installed the gnuradio on my mac pc(mac os sierra).I have two > questions: Welcome to GR on Mac! > 1.When I run some grc example,the grc will post a error.It > said"missing xterm executable".How to solve it? If you used the default

Re: [Discuss-gnuradio] GRCon16 videos

Hi Adam - We're still waiting to hear back from the videographers. We'll make an announcement on various lists once the videos are in place. Cheers! - MLD On Sun, Oct 2, 2016, at 11:47 PM, Adam Bacon wrote: > Does anyone know when the videos from GRCon16 are supposed to be posted?

[Discuss-gnuradio] Volk / UHD / GR on macOS 10.12 Sierra

Apple released its latest OS earlier this week, now called "macOS" (was Mac OS X): 10.12.0, codename "Sierra". The vast majority of projects that built for 10.11 and prior continue to work with 10.12, including Volk, UHD, and GNU Radio. In MacPorts, I committed changes to Qt4 (qt4-mac) to allow it

Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

Hi Andy - Thanks for your detailed thoughts on the subject matter. I think we're all in general agreement that there are 2 ways to do REP / REQ with respect to which is client and which is server. GR implements one of those ways, but could easily provide the other, too. It's just another way of

Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

Hi Francisco - Yes, I think having a generic ZMQ block would be awesome. Do you have an OOT module or block that does what you listed: a generic ZMQ block? If so, how do I gain access to it? This would save me lots of time! Thanks! - MLD On Thu, Jul 28, 2016, at 10:21 PM, Francisco Albani wrote:

Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

On Thu, Jul 28, 2016, at 06:44 PM, Johnathan Corgan wrote: > The ZMQ REQ/REP dataflow has the receiving end REQuest data from the > sending end when needed, which REPlies with a packet. It's a form of > flow control. > > From the GNU Radio perspective, streams flow into GNU Radio sinks to > exit

Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

On Thu, Jul 28, 2016, at 03:11 PM, Sylvain Munaut wrote: > > But this model doesn't work for the REP / REQ in Figure 2 > > "Request-Reply". I would expect the ZMQ REQ to be a GR sink but instead > > if is a source; likewise, I'd expect the ZMQ REP to be a GR source & it > > is instead a sink. > >

[Discuss-gnuradio] ZMQ REQ / REP naming Swap?

I'm trying to work with the ZQM REQ / REP message blocks while learning about ZMQ. From their overview guide < http://zguide.zeromq.org/page:all >, they define various graphs where the interconnects are the ZMQ connections. Thus, for example, in Figure 4 "Publish-Subscribe", the PUB would be GR

Re: [Discuss-gnuradio] couple of questions

__ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > -- Michael Dickens, Mac OS X Programmer Ettus Research Technical Support Email: supp...@ettus.com Web: http://www.ettus.com

Re: [Discuss-gnuradio] License for libs linked in OOT

What Sylvain wrote is correct: if you publish your GR OOT module, then you have to choose GPLv3 or a compatible FOSS license. I believe that by default the license is GPLv3, since that's what GR is. See also < http://www.gnu.org/licenses/license-list.html > for a list of compatible (and

Re: [Discuss-gnuradio] Macports Patch File

I'm replying right now off list to Mark's query. What he's asking is not of interest to most users; mostly for advanced developers. - MLD On Wed, Jul 6, 2016, at 10:02 AM, Mark Napier wrote: > Hello, > > With help from Michael I've made up a patch file for the db_tvrx.cpp > and dboard_iface.cpp.

Re: [Discuss-gnuradio] new user

Hi Darin - If you want to use SDRplay, you -can- do that using MacPorts via the gr-osmosdr port: with a patch that I can provide. The SDRplay folks, at least in the recent past: (1) provide only pre-combined binaries, not source code, which need to be tweaked to work for most OS X installs

Re: [Discuss-gnuradio] new user

I think if you follow the install guide for Mac OS X, GR will work almost out of the box. As stated, there are cases where some dependencies fail to build or the like; just "clean" the failed dependency, try to install it directly, and it usually works. Most dependencies are a binary download now;

Re: [Discuss-gnuradio] A basic question about writing OOT modules

HI Franz - I'd guess that GNU Radio isn't installed, or not installed into where CMake is installed & you're not telling CMake where to look. FindGnuradio.cmake looks for GnuradioConfig.cmake, which is located in some DIR/cmake/gnuradio directory. The DIR will be either PREFIX/lib or PREFIX/share,

Re: [Discuss-gnuradio] OS X Tutorial Problem fixed

You're welcome; glad that works! - MLD On Tue, Apr 26, 2016 at 6:08 AM, jim Schimpf <jim.schi...@gmail.com> wrote: > Thanks to Michael Dickens <michael.dick...@ettus.com>. The tutorial > problem in OS X I was having is fixed. Deleting the tutorial build > directory, a

Re: [Discuss-gnuradio] OS X GnuRadio Tutorial question

Hi Jim - Great to hear from another OS X GNU Radio user! The issue is likely that MacPorts' 'python' expects its packages to be installed into /opt/local somewhere, not /usr/local . I sure there's a way to set various environment variables to find the installed files, but it's easier to just

Re: [Discuss-gnuradio] Upgrading GR in MacPorts

On 03/21/2016 01:50 PM, Thomas Wagner wrote: > I will try to upgrade the installation on the Macbook to 3.9.1. It > took me all night on Saturday to get in on the Macmini, I kept > getting GnuRadio error messages on compile, I finally had to > uninstall it and start over, then it worked.

Re: [Discuss-gnuradio] Evaluation failure of oot module block

Hi chandan - Try setting the PYTHONPATH environment variable in your shell to include the /path/to/your/module, and make sure that the /path/to/FEC/module is also in the PYTHONPATH, if they were installed into different directories. All of the GR modules need to be in the PYTHONPATH somewhere in

Re: [Discuss-gnuradio] Help with OOT error

Hi micro7311 - GRC scripts are placed typically into ${prefix}/share/gnuradio/grc/blocks -- in your case, looks like ${prefix} == "/usr". Without having access to your OOT module or any other info about it, the best advice I can give is to check to make sure our OOT install ${prefix} matches that

Re: [Discuss-gnuradio] Help with OOT error

On Fri, Feb 12, 2016, at 08:32 AM, micro7311 wrote: > Hi, thank for the detailed response to my question.  I forgot to > attach the OOT modules.  They are attached here. All works nicely for me, though admittedly I'm running on OS X & you're not (or, looks like not). Here's a screenshot of one of

Re: [Discuss-gnuradio] CMake Error

Hi shortwavedude - You're trying to configure an OOT module, yes? (GNU Radio internally would not look for itself, so this is the logical conclusion. Which OOT module are you trying to build?) That error means that this OOT module is looking for GR 3.7.2 or newer, and that cmake can't find GR

Re: [Discuss-gnuradio] OOT module authors, please update your cmake

On Tue, Dec 29, 2015, at 07:31 PM, Johnathan Corgan wrote: > On Tue, Dec 29, 2015 at 4:10 PM, Michael Dickens <michael.dick...@ettus.com> > wrote: > >> My advice is to just update the whole cmake directory. There >> have been >> other changes in that directo

Re: [Discuss-gnuradio] OOT module authors, please update your cmake

On Tue, Dec 29, 2015, at 08:30 PM, Johnathan Corgan wrote: > On Tue, Dec 29, 2015 at 5:08 PM, Philip Balister wrote: >> Dunno, but gr-newmod (or whatever it is called) in gnuradio >> has a copy >> of the files. I had to fix the issue twice. > > This is good opportunity then

Re: [Discuss-gnuradio] OOT module authors, please update your cmake

My advice is to just update the whole cmake directory. There have been other changes in that directory that should be included in OOT modules too. I know not all OOT modules use the latest, because I patch them in MacPorts for the parts I need. - MLD On Tue, Dec 29, 2015, at 04:43 PM, Philip

Re: [Discuss-gnuradio] OOT module authors, please update your cmake

I believe that GR did not provide these files a while back, so we included them in the OOT via gr-modtool. They've been there ever since. That's my memory. - MLD On Tue, Dec 29, 2015, at 07:47 PM, Johnathan Corgan wrote: > On Tue, Dec 29, 2015 at 4:42 PM, Michael Dickens > <mic

Re: [Discuss-gnuradio] writing a python block

Hi chandan - I have your code in hand and will look at it soon. I'll email shortly with more info. - MLD On Tue, Dec 29, 2015, at 03:57 PM, chandan kumar wrote: > I have added a interpolator block in my out of tree module. The > interpolation factor of the block is of integer type and single

Re: [Discuss-gnuradio] Compatibility with Mac OS X

Hi Jeon - I maintain GNU Radio / Volk / UHD within MacPorts, and they generally work on OS X 10.8 through 10.11; I know of folks using than on 10.6/7, and I believe they can be coerced into working on 10.5 (Intel or PPC). There are issues here and there, such as that ControlPort doesn't really

Re: [Discuss-gnuradio] Discuss-gnuradio Digest, Vol 155, Issue 40

Hi Chandan - It looks like you did everything correctly. Can you send me a tarball archive of your OOT module to my email here & I'll help diagnose off-list. We can report back what we find if it's useful. - MLD On Sat, Oct 31, 2015, at 12:50 AM, chandan kumar wrote: > To install gnuradio, I

Re: [Discuss-gnuradio] out-of-tree module development on mac

Hi Chandan - What procedure did you follow? And, how is GNU Radio installed on your Mac? When you write that every command runs, do you mean that you have QA code that works? We need a little more info before we can really provide you assistance here. Feel free to email me directly & we can report

[Discuss-gnuradio] UHD / GNU Radio / Volk Compatibility with Mac OS X 10.11 "El Capitan"

Today (Wednesday, Sep 30), Apple released its latest OS for free download: 10.11 "El Capitan". This new OS comes with Xcode 7.0.1, which provides clang 7 (700.0.72) and (likely) llvm 3.7 -- both updates from those provided in Xcode 6 or Xcode 5. With each new Xcode generation, some APIs are

Re: [Discuss-gnuradio] Fatal Python error: PyThreadState_Get: no current thread (OSX 10.10.5, Homebrew install)

Hi David - It looks from the 'brew install log that brew is using "/usr/local/Cellar/python/2.7.10_2/bin/python", while you're trying to use "/usr/local/bin/python". These may or not be the same install of Python; given the PyThreadState_Get error you're getting I'd bet they are different

Re: [Discuss-gnuradio] import Qwt error

Hi Nemanja - SIP is used in Qwt and other PyQt related projects. It has its own internal API, which must be compatible for all Python modules being loaded (including SIP itself). So, what this error means is that the Qwt module was built using a given SIP API (6.0 looks like), then SIP was

Re: [Discuss-gnuradio] Fwd: Re: Transmission error

Hi Dave - I'm thinking that you are confusing "--samples-per-symbol" for the sample rate. I think the option you're looking for is "-r". Look at the "--help" for those examples when you get a chance. - MLD On Thu, Sep 17, 2015, at 02:01 PM, Rama V wrote: > Thank you very much Michael. I will

Re: [Discuss-gnuradio] Fwd: Re: Transmission error

Hi Rama/Dave - The benchmark examples run as standalone applications. They do require Python, but they do not use GRC or any other GUI interface. Question: Are you running the OFDM or Digital/Narrowband benchmark? What exact commands are you using for both Rx and Tx? What SDR hardware are you

Re: [Discuss-gnuradio] Problem with OOT module import

Hi Richard - Glad you got the runtime part worked out for your OOT block. CMake has its good and bad moments ... As for the why the QA code fails, since you're on Linux do you need to set the LD_LIBRARY_PATH somewhere? I know on OSX we have to "make install" before doing "make test" because the

Re: [Discuss-gnuradio] gnuradio runtimeerror

Hi CDL - As you also replied on the USRP list & this is a UHD and/or Ettus Research issue, not a GR issue, we're moving the discussion to just that email group & leaving this one. You'll still get support, just there & not here. - MLD On Thu, Sep 10, 2015, at 06:40 AM, cdl wrote: > i am using one

Re: [Discuss-gnuradio] Problem with OOT module import

What OS are you building on? On Thu, Sep 10, 2015, at 02:18 PM, Richard Bell wrote: > I wrote an OOT module in cpp using GNU Radio 3.7.8, it shows up in GRC > but when I run it, I get the worst error known to mankind (in my > opinion): > > AttributeError: 'module' object has no attribute

Re: [Discuss-gnuradio] GRCon15 statistics

Hi Francisco - I'm not sure we can definitely say how many people helped out; we sort of ebbed and flowed as necessary to make it work. There were another 2-6 of us meeting weekly (and emailing regularly) for organizational purposes; some more often than others. We had 15-20 volunteers to help

Re: [Discuss-gnuradio] 回复: gnuradio error

Please reply on-list for the best assistance; not to me or any specific responder personally. OK; so you're using a B200, and you're getting USB errors. Have you tried different cables? Have you tried different computers / different OSs or different OS versions? Anything else beyond the error you

Re: [Discuss-gnuradio] GNU Radio Installation Error

Hi Rama/Dave - I can't say -why- the error is happening, but the error is because for some reason the llibusb1 library is not being included in the linking. This might be because the libusb1 library has been updated since the last time GNU Radio was built; or, it might be for other reasons too;

Re: [Discuss-gnuradio] GRCon15 attendees

We're discussing what can be released & Tom will reply with that info. It will not include email addresses, names, or affiliations; it will probably be just # of registrations because we also can't accurately say the # who attended any given day. Anyway, more from him once he gets there. - MLD On

Re: [Discuss-gnuradio] gnuradio error

Hi cdl - Which USRP are you using? USRP1, B200, B210? Might make a difference ... - MLD On Wed, Sep 9, 2015, at 12:22 PM, cdl wrote: > i am using uhd model in gnuradio,usrp_sink and usrp_source to do a > loopback sysrem and i connect the usrp tx and rx withRF feeder > line,when i exe the grc ,i

Re: [Discuss-gnuradio] Running flowgraphs from command line

Hi Patrick - You're on the right track. We're just following what is written (roughly) in < http://gnuradio.org/redmine/projects/gnuradio/wiki/MacInstall >. Please also note that unless you play some tricks with the +quartz variant that is available many GR dependencies, you'll have to install

Re: [Discuss-gnuradio] [Discuss-GR] Running flowgraphs from command line

[off list] Hi Patrick - Thanks for the feedback. I've heard of your issue before; never experienced it myself. Do you mind if I ask you to do a few things to help debug & maybe we can figure out a better way to keep GR / Python / MP happy? I not, that's fine too; just thought I'd ask. 1) If you

Re: [Discuss-gnuradio] [Discuss-GR] Running flowgraphs from command line

My bad; let me really take this off list :) On Tue, Sep 8, 2015, at 02:07 PM, Michael Dickens wrote: > [off list] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Running flowgraphs from command line

Hi Patrick - So what's happening is that with GRC, because it was installed via MacPorts the MP version of Python is used. The terminal only knows what you tell it via environment variables such as PYTHONPATH (already suggested by Kevin Hofschröer) and PATH. In your case right now, I'll bet that

Re: [Discuss-gnuradio] Possible typos in a GRCon15 presentation?

Hi Jeon - It is quite possible that some presentations contain minor typos or even errors. Research/development and presentation of it is imperfect at best. Discussion such as this is the right thing to do! If anyone catches minor typos or errors in any GRCon15 presentation (or, for that matter,

Re: [Discuss-gnuradio] Dr Mitola's Keynote slides

Hi Jason - Our hope is to get slides from Dr Mitola as well as permission from Paul Tilghman / DARPA to release his slides. I have queries into both of them, and am waiting to hear back from the former. Maybe Tom can query Mitola specifically about this topic as well? No promises, but these are

Re: [Discuss-gnuradio] [USRP-users] [RFNoC] Tutorials @GRCon15

As a brief reiteration and follow-up regarding registration for this tutorial: In order to register for the RFNoC tutorial, you must be registered for the Developers Conference -- not just New Developers Day. If you have already registered for the Developers Conference, then you can just register

Re: [Discuss-gnuradio] Spending the whole day to build gnuradio on a Mac?

Hi Ton - As always, I recommend using MacPorts to do your dirty work; check out the GR install guide http://gnuradio.org/redmine/projects/gnuradio/wiki/MacInstall . Once 'port' is installed, getting GR is as simple as sudo port install gnuradio. For sdrplay: If you check out the Gqrx forum,

[Discuss-gnuradio] GRCon15 Registration Updates

We're heading into the final weeks before GRCon15, and registration has thus far been strong. The new developers day and the main conference are about 2/3 sold, which still leaves plenty of tickets. The RFNoC tutorial is sold out, and we still have 8 student tickets (+ 8 tickets still waiting for

Re: [Discuss-gnuradio] [RFNoC] Tutorials @GRCon15

Please note that if you have already registered for the conference, you can go back and register just for the RFNoC tutorial for free. As Martin wrote: This tutorial requires main conference registration. There are only 20 tutorial tickets available, and they are being claimed quickly. So if you

Re: [Discuss-gnuradio] OSX 10.10 QT segfaults

Hi Paul - I'll work with you off-list if we figure out something useful I'll report back to the list. - MLD On Fri, Jul 17, 2015, at 12:14 PM, Paul Garver wrote: I’m experiencing seg faults on QT applications in OS X 10.10, but WX graphics (and GR/GRC in general) work without issue. I’ve

Re: [Discuss-gnuradio] possible bug in gr_modtool

Hi Federico - Yes, that does seem like a bug. Looking at the top-level docs/doxygen/CMakeLists.txt, this command is: {{{ add_custom_command( OUTPUT ${BUILT_DIRS} COMMAND ${DOXYGEN_EXECUTABLE} ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR} DEPENDS

Re: [Discuss-gnuradio] possible bug in gr_modtool

with the modtool docs to know what to add as DEPENDS there. - MLD On Tue, Jul 14, 2015, at 12:57 PM, Martin Braun wrote: On 14.07.2015 07:11, Michael Dickens wrote: Hi Federico - Yes, that does seem like a bug. Looking at the top-level docs/doxygen/CMakeLists.txt, this command

Re: [Discuss-gnuradio] Cmake question

Hi Volker - Actually, the command you quote just sets the -version- of the library, not the name. The name is set by default as the target name, though one can change the name to something else via a similar set_target_properties command. Hope this helps! - MLD On Mon, Jul 6, 2015, at 07:01 AM,

Re: [Discuss-gnuradio] Numpy question

A quick look at the source reveals NumPy is used extensively in GNU Radio, but it is checked for by the gr-wxgui and grc modules only. So, most of GNU Radio can install properly even if NumPy is not installed or working. - MLD On Mon, Jul 6, 2015, at 03:43 PM, Volker Schroer wrote: That

Re: [Discuss-gnuradio] Numpy question

Yes, pmt_to_python.py does use numpy. But, it looks like none of the actual build for gnuradio-runtime (including pmt) requires numpy to be installed. So, it's just used post-install. Hence, maybe why it's not listed as a direct dependency? - MLD On Mon, Jul 6, 2015, at 04:16 PM, Volker Schroer

Re: [Discuss-gnuradio] Numpy question

Yes, pmt is required for gnuradio-runtime, which in turn is required for anything gnuradio. - MLD On Mon, Jul 6, 2015, at 04:08 PM, Volker Schroer wrote: That's right, but the problem is pmt. Is it really required for gnuradio to run ? ___

Re: [Discuss-gnuradio] OSX 10.10

Hi Ed - Sorry to hear of your continued suffering. I should have spotted this the first run around: the error is for /usr/local/include ... so, it looks like you have some cruft left over in /usr/local ! If you go to that directory look around, maybe you can just rm -rf everything in it? After

Re: [Discuss-gnuradio] OSX 10.10

Hi Ed - Sorry to hear of your troubles migrating / upgrading MacPorts. Yes, it can be a real pain. If you stick with default variants, then most of the ports will be downloaded as pre-compiled binary. If you just use MacPorts for GNU Radio related ports, then the easier way is to: 1) wipe all MP

Re: [Discuss-gnuradio] OSX 10.10

Hi Ed - When updating to a new major OS version (e.g., 10.[5-9] - 10.10), you'll need to reinstall MacPorts. The recommended migration procedure when using MacPorts is found at http://trac.macports.org/wiki/Migration . I, personally, just start from an empty disk, install the OS, migrate over my

[Discuss-gnuradio] GRCon15: Extended Deadline for Call For Presentations, Tutorials, and Posters

on EasyChair, which takes only a few minutes. The submission period will now close at the end of day on *Friday, May 15, 2015.* Best Regards, John Malsbury Michael Dickens Tom Rondeau ps We have a basic website up for GRCon15 http://www.trondeau.com/gnu-radio-conference-2015/ , which includes EventBright

[Discuss-gnuradio] GRCon15 Submissions and Registration Reminder

submit an abstract via EasyChair https://easychair.org/conferences/?conf=grcon15 . You will need to create an account, which takes only a few minutes. The submission period will close on *Friday, May 8, 2015.* Best Regards, John Malsbury Michael Dickens Tom Rondeau

[Discuss-gnuradio] GRCon15 Website Registration

becomes available, and will post to this list when significant information is added or changed. Best Regards, John Malsbury Michael Dickens Tom Rondeau ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo

[Discuss-gnuradio] GRCon15: Hotels

In case folks are wondering, there are quite a few hotels and other lodging places within easy walking distance of the GRCon15 venue: the Center for Strategic and International Studies [1]. For whatever reason, places of lodging near the CSIS are quite reasonably priced for Washington, DC right

Re: [Discuss-gnuradio] Dependee is newer than depender gr-3.7.7 verbose build (harmless?)

/depend.internal. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- Michael Dickens, Mac OS X Programmer Ettus Research Technical Support Email: supp...@ettus.com Web: http

[Discuss-gnuradio] GRCon15: Call For Presentations and Tutorials Reminder

and SDR please submit an abstract via EasyChair https://easychair.org/conferences/?conf=grcon15 . You will need to create an account, which takes only a few minutes.  The submission period will close on *Friday, May 8, 2015.* Best Regards, John Malsbury Michael Dickens Tom Rondeau

Re: [Discuss-gnuradio] gr::buffer::allocate_buffer: warning

On Tue, Apr 21, 2015, at 03:12 PM, Marcus Müller wrote: By the way: This currently *is* getting more interesting: Because you typically don't want to copy memory needlessly in a performance-critical application, it's bad that blocks that wrap some kind of accelerator (GPU, FPGA card, DSP

Re: [Discuss-gnuradio] gr-display-master install (was Re: Writing text to a QT GUI Window)

Hi John - where gnuradio is installed is the top-evel PREFIX into which GR is installed. In your case, this would be /usr/local, so you'd use: {{{ cmake -DCMAKE_INSTALL_PREFIX=/usr/local .. }}} Hope this helps. - MLD On Mon, Apr 20, 2015, at 10:45 AM, Murphy, John wrote: In the gr-display-master

Re: [Discuss-gnuradio] gr-display-master install (was Re: Writing text to a QT GUI Window)

Execute gnuradio-config-info --prefix to see the PREFIX into which GNU Radio was installed. The default PREFIX is /usr/local, yes. - MLD On Mon, Apr 20, 2015, at 11:54 AM, Murphy, John wrote: Saw the item below on the archive page (I get the digest). And, yes, /usr/local is correct,

Re: [Discuss-gnuradio] Clipping Complex Samples to +/- 1.0?

Hi John - There aren't a lot of choices to do clipping; this is basically: {{{ float* in = (float*) INPUT; float* out = (float*) OUTPUT; for(int nn=0; nnNUMBER; ++nn) { *out++ = std::max(std::min(*in++, 1.0),-1.0); } }}} You could use Volk's volk_32f_x2_max_32f and volk_32f_x2_min_32f kernel

Re: [Discuss-gnuradio] pybombs bombs

I just issued a pull request to fix this issue. The problem is that on a few systems, such as yours, unit32_t is undefined in the top-level namespace, and should really be boost::uint32_t anyway to match the actual values being compared. This fix is just for a test, so it won't make any difference

Re: [Discuss-gnuradio] Failed to install gnuradio with PyBOMBS

Ok; my PR will remove that header, so hopefully it'll take care of the issue. - MLD On Wed, Apr 1, 2015, at 09:49 PM, Ron Economos wrote: In your previous pull request, you deleted the line: #include complex.h in gr-dtv/lib/dvbt2/dvbt2_paprtr_cc_impl.cc This would directly fix the build

Re: [Discuss-gnuradio] Failed to install gnuradio with PyBOMBS

wrote: I believe Michael Dickens will have a comprehensive fix for issues like this soon. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] grc and wxpython =3.0

I haven't seen a reply to this posting, so you're getting my Mac OS X / MacPorts-centric view. MacPorts has been using WX = 3.0 for quite a while now; currently at 3.0.2. I've done extensive testing with version 3.0 of WX and GNU Radio, and found nothing incompatible that wasn't already an issue

Re: [Discuss-gnuradio] SWIG 3.0.3 Issue

I sent the primary SWIG maintainer (William S Fulton) an email, and got a prompt reply forwarding my email to the SWIG developer's list. He primarily just verified and checked in the changes (that Tom found and quoted, below); he hopes that some of the SWIG developers can help him figure out

[Discuss-gnuradio] SWIG 3.0.3 Issue

SWIG 3.0.3 was released today (30 Dec 2014) http://www.swig.org/ , and I maintain this port in MacPorts. So, I naturally was curious to see if it works with GNU Radio. Sadly, GNU Radio fails because some of the SWIG-generated Python scripts have errors in them. For example, in SWIG 3.0.2 the

Re: [Discuss-gnuradio] gnuradio on OS X without X11

That's cool, Kai! Can you send me (off list) screenshots of GRC working? I tried the Quartz GTK interface quite a while back but it didn't work; it's good to know that it's working for -someone-, even if turns out to be just on a specific OS/install. That's progress! Thanks for reporting! - MLD

Re: [Discuss-gnuradio] segfault

Hi Michele - It looks like there are multiple GNU Radio installs being caught in the execution: /usr/local/lib/ and /usr/lib/x86_64-linux-gnu/ : {{{ Program received signal SIGSEGV, Segmentation fault. 0x76001d2f in pmt::string_to_symbol(std::string const) () from /

Re: [Discuss-gnuradio] Building GNURadio on Mac 10.9.5 using Homebrew Problems

Hi Ed - The actual link command was not included in the output you provided, so it’s difficult to say exactly where the issue lies. But, the basic cause is that “libSDL.dylib” is not being included in the link command, and/or it does not contain the various “SDL_*” symbols that are not being

<    1   2   3   4   5   6   7   8   9   10   >