Hi Richard, I've gotten rid of my CentOS 6.5 VM in favor of CentOS 7, where this was not an issue. However, usually "broken links" should not happen in CentOS. Did you "yum clean all", "yum check-updates" before installation? That should make absolutely sure only the newest packet lists from the official servers are used. As a general reference for CentOS users: It often seems very helpful to use the EPEL archives [1], which basically adds most of the packages that are missing in RHEL, CentOS and Scientific Linux compared to Fedora.
Greetings, Marcus [1] https://fedoraproject.org/wiki/EPEL On 01/16/2015 09:41 PM, Richard Bell wrote: > Thanks for that Martin. I enjoy learning things like this. What it > shows is gnuradio-companion is disabled because it does not recognize > pygtk installed. > > For whatever reason, the package-manager system on my centos 6.6 > machine has a broken link for pygobject and pygtk. I can't depend on > yum or pybombs to install it for me. > > I've downloaded pygobject from here: > http://ftp.gnome.org/pub/GNOME/sources/pygobject/2.27/ > > I've downloaded pygtk from here: > http://ftp.gnome.org/pub/GNOME/sources/pygtk/2.17/ > > I've been struggling for hours trying to get pygobject installed > correctly so that pygtk recognizes it as being installed. Extracting > pygobject to pybombs/src/pygobject I run ./configure, make, sudo make > install. No errors arise and I see a new file create in my /usr/local/bin > > When I then extract pygtk to pybombs/src/pygtk and run ./configure, I > receive the following partial output: > > checking for GLIB - version >= 2.8.0... yes (version 2.28.8) > checking for PYGOBJECT... configure: error: Package requirements > (pygobject-2.0 >= 2.16.1) were not met: > > No package 'pygobject-2.0' found > > My path variable includes all the standard locations and I did not > change the default install location of pygobject. > > I'm at my wits end with this. Help would be greatly appreciated. > > > P.S. Is it possible to fix this error with a yum repo hack? > > --2015-01-16 11:56:19-- > http://ftp.gnome.org/pub/GNOME/sources/pygobject/2.27/pygobject-2.27.91.patched.tar.gz > Resolving ftp.gnome.org... 130.239.18.165, 130.239.18.163, > 130.239.18.173, ... > Connecting to ftp.gnome.org > <http://ftp.gnome.org>|130.239.18.165|:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: > http://gensho.acc.umu.se/pub/GNOME/sources/pygobject/2.27/pygobject-2.27.91.patched.tar.gz > [following] > --2015-01-16 11:56:19-- > http://gensho.acc.umu.se/pub/GNOME/sources/pygobject/2.27/pygobject-2.27.91.patched.tar.gz > Resolving gensho.acc.umu.se... 130.239.18.176, 2001:6b0:e:2018::176 > Connecting to gensho.acc.umu.se > <http://gensho.acc.umu.se>|130.239.18.176|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2015-01-16 11:56:19 ERROR 404: Not Found. > > The ftp link it's using is correct, but for a filename error: > > This: > http://gensho.acc.umu.se/pub/GNOME/sources/pygobject/2.27/pygobject-2.27.91.patched.tar.gz > > Should be > http://gensho.acc.umu.se/pub/GNOME/sources/pygobject/2.27/pygobject-2.27.91.tar.gz > > Removed patched from the tarball filename. I don't know how pybombs > determines that link. > > v/r, > Rich > > On Thu, Jan 15, 2015 at 11:44 PM, Martin Braun <martin.br...@ettus.com > <mailto:martin.br...@ettus.com>> wrote: > > On 01/16/2015 02:10 AM, Richard Bell wrote: > > I've used pybombs to install uhd+gnuradio on CentOS 6.6 x86_64. > > > > I then executed ./pybombs env and sourced the generated file in > my .bashrc. > > > > After completely restarting my computer to make sure nothing > funny was > > going on, my terminal continues not to recognize > gnuradio-companion as a > > command. I can, however, run gnuradio-config-info. Some output that > > might be useful: > > > > gnuradio-config-info -v: v3.7.6.1-41-g0bea2cce > > gnuradio-config-info --builddate: Fri, 16 Jan 2015 00:18:57 > (date/time > > wrong here, not sure why) > > > > What could cause this behavior? I'm not sure how to debug this. > > Was GRC even built? Run "cmake .." from the GNU Radio build directory > (usually something like pybombs/src/gnuradio/build) and see if it's > among the enabled components. > > M > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org <mailto: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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
