Re: [Discuss-gnuradio] gr_modtool error when attempting to create Python tagged_stream block

[CEL]

Hi Sebastian,
in the future, could you please emails to the mailing list instead of
only to me? Others will be interested, too :) 
Thank you! 

Yeah, no, PyBOMBS was an attempt to solve the issue that we basically
had no recent packaging on any platform. We've luckily been able to
change that, or rather, good things happened to us. PyBOMBS is still a
cool tool, if you need to work with a prefix for embedded development.

No, that issue being raised for 3.8 is not sufficient, because there's
significant difference between the templates for these versions. 

Cheers,
Marcus

On Fri, 2019-05-17 at 17:16 +0200, Sebastian Sahlin wrote:
> Hi,
> 
> 1. The issue has already been raised, albeit for 3.8, perhaps that is 
> sufficient? https://github.com/gnuradio/gnuradio/issues/2489
> 2. I was under the impression that using PyBombs was to be preferred in order 
> to get the latest stable releases :P 
> 
> By the way: using apt to install GR on Ubuntu 18.04.2 got me 3.7.11, and I 
> receive the same error with gr_modtool trying to create a tagged_stream 
> block. 
> 
> Regards
> 
> Den fre 17 maj 2019 kl 16:58 skrev Müller, Marcus (CEL) <address@hidden>:
> > Ah, nice, so that's the latest maint-3.7 version (i.e. the latest
> > released version).
> > 
> > Two realizations set in:
> > 
> > 1. Unlike 3.8-tech-preview, where we still expect a bit of breakage,
> > this is surprising. You should definitely be able to do this. We'll
> > look into this. If you want, you can set up an issue on Github yourself
> > (advantage: you get notified when we have a solution), or we do that.
> > What would you prefer?
> > 2. If you're not after developing GNU Radio itself, but really only
> > using it, I'd really recommend using your Linux distro's package
> > manager (looking at your file paths, that's likely "apt") to install
> > GNU Radio next time (assuming you've got Ubuntu>18.10 or current
> > debian). Less hassle than building it from source using PyBOMBS, same
> > result. 
> > 
> > Best regards,
> > Marcus
> > 
> > On Fri, 2019-05-17 at 14:44 +0000, Müller, Marcus (CEL) wrote:
> > > -------- Forwarded Message --------
> > > > Hi Marcus,
> > > > 
> > > > The output from gnuradio-config-info --version is the follwing: 3.7.13.5
> > > > 
> > > > Regards
> > > > 
> > > > 
> > > > Den fre 17 maj 2019 kl 16:15 skrev Müller, Marcus (CEL) 
> > > > <address@hidden>:
> > > > > Hi Sebastian,
> > > > > 
> > > > > I know this sounds a bit silly, but could you actually tell us the
> > > > > version that `gnuradio-config-info --version` reports? We're kind of 
> > > > > in
> > > > > the process of getting new versions out, and I'm not quite sure what
> > > > > different people get when they use PyBOMBS.
> > > > > (also, almost certain you shouldn't have to use PyBOMBS if you just
> > > > > want to install a non-development version of GNU Radio; if you just
> > > > > want to install GNU Radio, use a recent Linux distro or OS X, you get 
> > > > > a
> > > > > modern GNU Radio that works through the usual apt,dnf,pac,…
> > > > > installation method.)
> > > > > 
> > > > > Thank you,
> > > > > Marcus
> > > > > On Fri, 2019-05-17 at 16:00 +0200, Sebastian Sahlin wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > I get the following output when trying to create a tagged stream 
> > > > > > block with the modtool using Python as the language: 
> > > > > > https://pastebin.com/D6gKJ2aS
> > > > > > 
> > > > > > GNURadio and gr_modtool version is the latest as installed with 
> > > > > > pybombs.
> > > > > > 
> > > > > > Regards,
> > > > > > Sebastian
> > > > > > 
> > > > > >  
> > > > > > _______________________________________________
> > > > > > Discuss-gnuradio mailing list
> > > > > > address@hidden
> > > > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > > 
> > > _______________________________________________
> > > Discuss-gnuradio mailing list
> > > address@hidden
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

smime.p7s
Description: S/MIME cryptographic signature