Re: [Discuss-gnuradio] Problem installing GR via pybombs on fresh load

[Martin Braun]

I've made the recipe prefer swig2.0, but it's not a full fix.

-- M

On 02/17/2017 07:53 PM, scott s wrote:
> I too ran into the same problem with SWIG on an Ubuntu 14.04.05 64bit
> install. For whatever reason, GNU Radio doesn't like the installed
> version of SWIG from the Ubuntu repositories
> (swig3.0_3.0.2-1ubuntu1~ubuntu14.04.1_amd64.deb). I was unable to
> determine why.
> 
> These are the steps I used, and attached a verbose log to the list. This
> was a bare install with no upgrades, and the latest version of PyBOMBS.
> 
> sudo apt-get update
> sudo apt-get install git build-essential python-pip
> sudo pip install git+https://github.com/gnuradio/pybombs.git
> 
> pybombs recipes add gr-recipes
> git+https://github.com/gnuradio/gr-recipes.git
> pybombs recipes add gr-etcetera
> git+https://github.com/gnuradio/gr-etcetera.git
> pybombs -vv prefix init ~/target -a sdr -R gnuradio-stable
> 
> Hope this helps.
> -Scott
> 
> 
> On 02/08/2017 03:35 PM, Martin Braun wrote:
>> 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
> 
> 
> ___
> 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

[Martin Braun]

Yeah, that's odd. SWIG 3.0.3 and 3.0.4 are blacklisted, but 3.0.2 is not.

Hmm

-- M

On 02/17/2017 07:53 PM, scott s wrote:
> I too ran into the same problem with SWIG on an Ubuntu 14.04.05 64bit
> install. For whatever reason, GNU Radio doesn't like the installed
> version of SWIG from the Ubuntu repositories
> (swig3.0_3.0.2-1ubuntu1~ubuntu14.04.1_amd64.deb). I was unable to
> determine why.
> 
> These are the steps I used, and attached a verbose log to the list. This
> was a bare install with no upgrades, and the latest version of PyBOMBS.
> 
> sudo apt-get update
> sudo apt-get install git build-essential python-pip
> sudo pip install git+https://github.com/gnuradio/pybombs.git
> 
> pybombs recipes add gr-recipes
> git+https://github.com/gnuradio/gr-recipes.git
> pybombs recipes add gr-etcetera
> git+https://github.com/gnuradio/gr-etcetera.git
> pybombs -vv prefix init ~/target -a sdr -R gnuradio-stable
> 
> Hope this helps.
> -Scott
> 
> 
> On 02/08/2017 03:35 PM, Martin Braun wrote:
>> 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
> 
> 
> ___
> 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

[Cinaed Simson]

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

Re: [Discuss-gnuradio] Problem installing GR via pybombs on fresh load

[Martin Braun]

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

[Garver, Paul W]

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

[Jason Matusiak]

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

[Garver, Paul W]

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] Problem installing GR via pybombs on fresh load

[Jason Matusiak]

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