Martin: I'm rebuilding from scratch this night. I'll modify the recipe for networkx before starting, and if it works, I'll.. what? submit a pull request? Well, first time for everything.
Nathan: As in, installing graphviz and pygraphviz should have been dependencies for networkx, not something we should need to worry about? Yeah, probably makes sense. All the best Laur 2016-03-23 19:50 GMT+02:00 West, Nathan <[email protected]>: > It sounds like networkx is only part of the issue and maybe there's an > upstream bug that Tom has patched over locally. Is this something we should > report upstream to the distros? > > > On Wednesday, March 23, 2016, Martin Braun <[email protected]> wrote: > >> Laur, >> >> can you please submit a recipe to gr-recipes for networkx? >> >> Thanks, >> Martin >> >> On 03/23/2016 01:50 AM, Laur Joost wrote: >> > Thanks for the responses, and damned be the timezones. >> > >> > Nathan: gr-perf-monitorx needs python-networkx (which is installed by >> > pybombs, or at least, existed for me), but python-networkx needs >> > python-pygraphviz, at least for how it's used by gr-perf-monitorx. >> > >> > Tom: Yes, the errors popped up when networkx called agraph-something. >> > Sadly, I managed to blow up my installation, so can't get a traceback >> > for you (was able to reproduce by simply doing apt-get uninstall >> graphviz). >> > >> > On another note (the blowing up), I had an issue with gr-uhd ABI >> versions: >> > When trying to use USRP on the same install, I got: >> > >> > Traceback (most recent call last): >> > File "/home/ec/Tests/top_block.py", line 167, in <module> >> > main() >> > File "/home/ec/Tests/top_block.py", line 155, in main >> > tb = top_block_cls() >> > File "/home/ec/Tests/top_block.py", line 69, in __init__ >> > channels=range(1), >> > File >> > >> "/home/ec/gnuradio/lib/python2.7/dist-packages/gnuradio/uhd/__init__.py", >> line >> > 122, in constructor_interceptor >> > return old_constructor(*args) >> > File >> > >> "/home/ec/gnuradio/lib/python2.7/dist-packages/gnuradio/uhd/uhd_swig.py", >> line >> > 1973, in make >> > return _uhd_swig.usrp_source_make(*args) >> > RuntimeError: >> > GR-UHD detected ABI compatibility mismatch with UHD library. >> > GR-UHD was build against ABI: 3.9.0-0, >> > but UHD library reports ABI: 3.10.0-0 >> > Suggestion: install an ABI compatible version of UHD, >> > or rebuild GR-UHD component against this ABI version. >> > >> > However, install log shows: >> > >> > Configuring gr-uhd support... >> > -- Dependency Boost_FOUND = 1 >> > -- Dependency UHD_FOUND = TRUE >> > -- Dependency ENABLE_GNURADIO_RUNTIME = ON >> > -- Dependency ENABLE_GR_FILTER = ON >> > -- Dependency ENABLE_GR_BLOCKS = ON >> > -- Dependency ENABLE_GR_ANALOG = ON >> > -- Enabling gr-uhd support. >> > -- Override with -DENABLE_GR_UHD=ON/OFF >> > -- UHD Version: 3.10.git >> > >> > I had UHD 3.9.1 installed via package manager (wasn't as thorough as I'd >> > hoped in cleaning gnuradio 3.7.8 from the system), but if the detected >> > version in the log was 3.10, I would've thought that that would be the >> > version built against. I guess its mostly PEBKAC, but still, weird. >> > >> > I'll try building again this night, this time without 3.9 installed. If >> > the issue persists, I'll make another thread. >> > >> > 2016-03-23 1:30 GMT+02:00 Tom Rondeau <[email protected] >> > <mailto:[email protected]>>: >> > >> > On Tue, Mar 22, 2016 at 7:05 PM, West, Nathan >> > <[email protected] <mailto:[email protected]>> >> > wrote: >> > >> > Sorry, may or may not be talking about the same thing here. >> > gr-perf-monitorx requires python-networkx, which (I think) is an >> > untracked dependency. >> > >> > >> > >> > For utilities like this, we have not previously made Python modules >> > a required dependency of GNU Radio. We could, but that would put an >> > extra burden on just building the project even if you don't use the >> > particular app or example. Generally, we try to provide a friendly >> > message explaining the problem. PyBOMBS probably should add these >> > dependencies, though. At least scipy. >> > >> > Also, I believe I ran into this issue recently new versions of >> > networkx that broke out a dependency that used to not be required as >> > a separate install, which I think is what the OP's problem is >> > related to. See PR #768: >> > >> > https://github.com/gnuradio/gnuradio/pull/768 >> > >> > Tom >> > >> > >> > >> > >> > On Tue, Mar 22, 2016 at 7:04 PM, West, Nathan >> > <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > gr-perf-monitorx. It's just been the kind of thing that >> > everyone that uses it already has and no one tracks it. >> > There's a couple of minor deps for utilities like this that >> > sneak through the cracks, but they're very hard to keep >> > track of until you run this on a brand new image. >> > >> > nw >> > >> > On Tue, Mar 22, 2016 at 6:46 PM, Martin Braun >> > <[email protected] <mailto:[email protected]>> >> wrote: >> > >> > Who is calling pygraphviz? If we need this for GNU >> > Radio, we probably >> > need to update some recipes. >> > >> > M >> > >> > On 03/22/2016 12:12 PM, Laur Joost wrote: >> > > Hi all! >> > > >> > > Fresh install of gnuradio-3.7.9.1 via PyBOMBS-2.0.1 on >> > Ubuntu 15.10 >> > > >> > > When trying to run CrtlPort Performance Monitor on a >> > fresh 3.7.9.1 >> > > install, I got errors about missing pygraphviz. >> > > >> > > sudo apt-get python-pygraphviz >> > > >> > > solved it for me. The supposedly equivalent >> > > >> > > sudo apt-get install graphviz >> > > [sudo apt-get install graphviz-dev libgraphviz-dev] >> > > pip install pygraphviz >> > > >> > > threw a bunch of errors and claimed to be successful, >> > but didn't work. >> > > So beware PyPI, in this case. >> > > >> > > >> > > _______________________________________________ >> > > Discuss-gnuradio mailing list >> > > [email protected] <mailto: >> [email protected]> >> > > >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > > >> > >> > >> > _______________________________________________ >> > Discuss-gnuradio mailing list >> > [email protected] <mailto: >> [email protected]> >> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > >> > >> > >> > >> > _______________________________________________ >> > Discuss-gnuradio mailing list >> > [email protected] <mailto:[email protected]> >> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > >> > >> > >> > _______________________________________________ >> > Discuss-gnuradio mailing list >> > [email protected] <mailto:[email protected]> >> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > >> > >> > >> > >> > _______________________________________________ >> > Discuss-gnuradio mailing list >> > [email protected] >> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > >> >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> [email protected] >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > >
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
