[Discuss-gnuradio] Problem installing GR via pybombs on fresh load
Two different coworkers recently mentioned to me that on fresh Ubuntu machines, they were having trouble getting GR to install via pybombs. It was the case (which I've seen before) where it acts like it installed, but source setup_env.sh doesn't source the gnuradio-companion binary. If you run the binary directly, a window pops up complaining about Python paths. The fix for both of them seemed to be wiping everything out and installing swig (one of them figured this out by installing with the -vv option and looking at the output). Then when they installed GR everything seemed to be happy. So i just wanted to mention that you may need to add that to your requirements in your documentation. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Problem installing GR via pybombs on fresh load
I just saw this too a few days ago on Ubuntu (14.04/15.04, can’t remember). It appears to me that although GR builds, it builds without any Python support because SWIG isn’t found / installed. I don’t think this is a documentation issue - it’s a Pybombs issue. PWG > On Feb 8, 2017, at 8:52 AM, Jason Matusiak > wrote: > > Two different coworkers recently mentioned to me that on fresh Ubuntu > machines, they were having trouble getting GR to install via pybombs. It was > the case (which I've seen before) where it acts like it installed, but source > setup_env.sh doesn't source the gnuradio-companion binary. If you run the > binary directly, a window pops up complaining about Python paths. > > The fix for both of them seemed to be wiping everything out and installing > swig (one of them figured this out by installing with the -vv option and > looking at the output). Then when they installed GR everything seemed to be > happy. > > So i just wanted to mention that you may need to add that to your > requirements in your documentation. > > ___ > 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] Problem installing GR via pybombs on fresh load
I can verify that the one guy was using 14.04. The other guy also was mucking with 16.04 and got it working, but I can't say with 100% that he didn't install other packages while fuming at pybombs. I can see saying that it is a pybombs issue, but you say that swig it is a pre-req, that would be fine. On the other hand, it is a little odd that pybombs is willing to say that everything installed fine when it obviously didn't. On 02/08/2017 09:02 AM, Garver, Paul W wrote: I just saw this too a few days ago on Ubuntu (14.04/15.04, can’t remember). It appears to me that although GR builds, it builds without any Python support because SWIG isn’t found / installed. I don’t think this is a documentation issue - it’s a Pybombs issue. PWG On Feb 8, 2017, at 8:52 AM, Jason Matusiak wrote: Two different coworkers recently mentioned to me that on fresh Ubuntu machines, they were having trouble getting GR to install via pybombs. It was the case (which I've seen before) where it acts like it installed, but source setup_env.sh doesn't source the gnuradio-companion binary. If you run the binary directly, a window pops up complaining about Python paths. The fix for both of them seemed to be wiping everything out and installing swig (one of them figured this out by installing with the -vv option and looking at the output). Then when they installed GR everything seemed to be happy. So i just wanted to mention that you may need to add that to your requirements in your documentation. ___ 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
[Discuss-gnuradio] OFDM channel etimation
Hi, I want to estimate the channel (h) using OFDM. I am using rx_OFDM.grc flow graph for OFDM implementation. According to my knowledge, I can find channel from the output of OFDM channel estimation block. The channel is present on tags. But how can I extract channel form these tags. If I connect the tag debug block with complex type, would I get the chennel? Please guide if possible. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Usage of GitHub
Hi Svetlana, I get your concerns, but AFAIK it's currently very unlikely that GNU Radio will leave GitHub. It is still the place-to-be for open source code. If you feel uncomfortable using GitHub, we also have the repo self-hosted at http://gnuradio.org/redmine/projects/gnuradio/repository . Best, Sebastian On 06.02.2017 23:03, Svetlana Tkachenko wrote: > Please do not use github. It runs non-free JavaScript, hosts non-free > software discover-able by its users, and encourages poor licensing > practices. https://www.gnu.org/software/repo-criteria-evaluation.html > has extra information. I believe a GNU project may not refer users to > non-free resources in this manner. > > I believe as an alternative, a Gogs instance provides functionality > similar to GitHub and may be self-hosted. > > ___ > 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] Usage of GitHub
On 02/06/2017 05:03 PM, Svetlana Tkachenko wrote: Please do not use github. It runs non-free JavaScript, hosts non-free software discover-able by its users, and encourages poor licensing practices. https://www.gnu.org/software/repo-criteria-evaluation.html has extra information. I believe a GNU project may not refer users to non-free resources in this manner. I believe as an alternative, a Gogs instance provides functionality similar to GitHub and may be self-hosted. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio I'm going to paraphrase your position, to highlight the absurdity of it: "Please don't house Gnu projects in buildings in which other, non-free, software development takes place, also, not in cities in which the by-laws allow such non-free entities to conduct business". Can you see how absurd your position is? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Problem installing GR via pybombs on fresh load
Well, since SWIG just wraps the C++ API into Python, it isn’t really required. The bigger issue to me is essentially a pybombs feature request. It would be nice if you could clearly see which GR modules are enabled/disabled, or force Pybombs to quit if certain dependencies aren’t met to build a particular module. This happens all the time in SDR builds since people need many different configurations. The user should be able to specify required GR modules in the recipe somehow, or at least have a verbose information statement about that module not having dependencies met. PWG > On Feb 8, 2017, at 9:36 AM, Jason Matusiak > wrote: > > I can verify that the one guy was using 14.04. The other guy also was > mucking with 16.04 and got it working, but I can't say with 100% that he > didn't install other packages while fuming at pybombs. > > I can see saying that it is a pybombs issue, but you say that swig it is a > pre-req, that would be fine. On the other hand, it is a little odd that > pybombs is willing to say that everything installed fine when it obviously > didn't. > > On 02/08/2017 09:02 AM, Garver, Paul W wrote: >> I just saw this too a few days ago on Ubuntu (14.04/15.04, can’t remember). >> It appears to me that although GR builds, it builds without any Python >> support because SWIG isn’t found / installed. I don’t think this is a >> documentation issue - it’s a Pybombs issue. >> >> PWG >> >>> On Feb 8, 2017, at 8:52 AM, Jason Matusiak >>> wrote: >>> >>> Two different coworkers recently mentioned to me that on fresh Ubuntu >>> machines, they were having trouble getting GR to install via pybombs. It >>> was the case (which I've seen before) where it acts like it installed, but >>> source setup_env.sh doesn't source the gnuradio-companion binary. If you >>> run the binary directly, a window pops up complaining about Python paths. >>> >>> The fix for both of them seemed to be wiping everything out and installing >>> swig (one of them figured this out by installing with the -vv option and >>> looking at the output). Then when they installed GR everything seemed to >>> be happy. >>> >>> So i just wanted to mention that you may need to add that to your >>> requirements in your documentation. >>> >>> ___ >>> 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] Problem installing GR via pybombs on fresh load
Like you say, people shouldn't be installing Swig by hand. It should just work. Now, why isn't it working? That would be great to know. It helps if you guysers could post logs from the installs, preferably with -vv verbosity. How do I test this stuff? PyBOMBS has some Docker-based testing built into the repo. For most distros, this'll spin up the appropriate Docker, and then install everything from scratch. I know it installs SWIG then. The problem is, when people run on their own desktop, there might be all kinds of settings and configurations going on. For those specific, situations, we need more and better bug reports. Obviously, suggestions for fixes (and actual fixes) are also important. So, please submit those whenever stuff fails. Thanks, Martin On 02/08/2017 06:52 AM, Garver, Paul W wrote: > Well, since SWIG just wraps the C++ API into Python, it isn’t really > required. The bigger issue to me is essentially a pybombs feature request. It > would be nice if you could clearly see which GR modules are enabled/disabled, > or force Pybombs to quit if certain dependencies aren’t met to build a > particular module. > > This happens all the time in SDR builds since people need many different > configurations. The user should be able to specify required GR modules in the > recipe somehow, or at least have a verbose information statement about that > module not having dependencies met. > > PWG >> On Feb 8, 2017, at 9:36 AM, Jason Matusiak >> wrote: >> >> I can verify that the one guy was using 14.04. The other guy also was >> mucking with 16.04 and got it working, but I can't say with 100% that he >> didn't install other packages while fuming at pybombs. >> >> I can see saying that it is a pybombs issue, but you say that swig it is a >> pre-req, that would be fine. On the other hand, it is a little odd that >> pybombs is willing to say that everything installed fine when it obviously >> didn't. >> >> On 02/08/2017 09:02 AM, Garver, Paul W wrote: >>> I just saw this too a few days ago on Ubuntu (14.04/15.04, can’t remember). >>> It appears to me that although GR builds, it builds without any Python >>> support because SWIG isn’t found / installed. I don’t think this is a >>> documentation issue - it’s a Pybombs issue. >>> >>> PWG >>> On Feb 8, 2017, at 8:52 AM, Jason Matusiak wrote: Two different coworkers recently mentioned to me that on fresh Ubuntu machines, they were having trouble getting GR to install via pybombs. It was the case (which I've seen before) where it acts like it installed, but source setup_env.sh doesn't source the gnuradio-companion binary. If you run the binary directly, a window pops up complaining about Python paths. The fix for both of them seemed to be wiping everything out and installing swig (one of them figured this out by installing with the -vv option and looking at the output). Then when they installed GR everything seemed to be happy. So i just wanted to mention that you may need to add that to your requirements in your documentation. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Problem installing GR via pybombs on fresh load
On 02/08/2017 05:52 AM, Jason Matusiak wrote: > Two different coworkers recently mentioned to me that on fresh Ubuntu > machines, they were having trouble getting GR to install via pybombs. > It was the case (which I've seen before) where it acts like it > installed, but source setup_env.sh doesn't source the gnuradio-companion > binary. If you run the binary directly, a window pops up complaining > about Python paths. > > The fix for both of them seemed to be wiping everything out and > installing swig (one of them figured this out by installing with the -vv > option and looking at the output). Then when they installed GR > everything seemed to be happy. > > So i just wanted to mention that you may need to add that to your > requirements in your documentation. > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > . > If it's a PYTHONPATH issue, no need to re-install. Is PYTHONPATH defined in your environment? And does PYTHONPATH include a path for your gnuradio installation? Type env | grep PYTHONPATH Do you have multiple installs of python? For instance, you might be using python 3 by default but pybombs used python 2 - or some other combination - if it's a problem it's easy to check. Fire up python and type import os pythonpath=os.environ['PYTHONPATH'].split(os.pathsep) print pythonpath -- Cinaed ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
