Re: Python errors running flowgraph - first attempt

I don’t have a solution for this yet either, but I have made some
“progress”. I decided to try and build PyQwt-5.2.0 and see what

Summarizing things we already found:

The starting point for this effort was an SD Card newly generated from
sdimage-gnuradio-demo-direct.xz file that Phillip posted at: the other day. As
one would expect once I modifed /etc/ssh/sshd_config, setting
to yes and reset X I could X in and run GRC from my 14.04 Ubuntu VM.

The first thing I noted was that:

  1. There are spurious \n’s after the *'s in the file
    /usr/lib/python2.7/site-packages/PyQt4/ in the instance that is
    on the E310 that need to be removed in order to not cause an error.

  2. In order to run GRC you need to run it
    with LD_PRELOAD=“/usr/lib/
    /usr/lib/ /usr/lib/
    /usr/lib/” gnuradio-companion

This get you to the point where running a flowgraph with QtGUI widgets
it complains that the is no QWT

First, when one tries to install the PyQwt-5.2.0 code by running:

python -Q …/qwt-5.2

A message is generated by that indicates “Requires at least
PyQt-4.2 and it’s development tools”. This appeared to be a result of a
change in the way PyQt4 pyqtconfig is dealt with from version to
The notes on pyqtconfig in this link:

give some indication of this as well as information found here:

This I got past by placing a copy of that I found in my
Ubuntu 14.04 VM version implementation into the E310’s

/usr/lib/python2.7/site-packages/PyQt4 directory

I also found that when I tried to run from the command
it complained about not having and so I found a copy of and on the Ubuntu 14.04 VM version and put
them in the /usr/lib/python2.7/site-packages on the E310.

This got me farther on the path towards trying to build PyQwt on the
but issues still remained further downstream of the “Requires at least
PyQt-4.2 and it’s development tools” message.

I believe this was all that was required to get past the invalid version
message. Although I also copied the folder Qwt5 from
to a new folder on the E310 by that name in that location and I copied
file folder named Qwt5 from the /usr/lib/python2.7/dist-packages/Pyqt4
folder to the /usr/lib/python2.7/site-packages/PyQt4 directory on the
… I knew that the two .so files ( and would likely not
work because of a need to crosscompile them but I figured, Python is
Python … Ididn’t copy any .pyc files figuring they would get
automatically and they were.

Once I had done these things I did in fact get past the "Missing Qwt5
message in GRC, but as expected I came to the message about the invalid
format of the .so files.

I was hoping to find the .so files on one of my SD cards from Zedboard
from the original release version of the E310 code, but neither of these
appear to have PyQt4 on them at all.

As I have been unable to get the build complete, even on the 14.04 VM
natively I thought I’d go back to trying to do this in preparation for
trying to crosscompile the missing .so files.

I didn’t keep real good notes on what hurtles I faced with this, but I
to the point where python -Q …/qwt-5.2 was failing with:

sip:Unable to find file QtCore/QtCoremod.sip SIP failed to generate C++

I found that I needed to sudo apt-get install python-qt4-dev and once I
this the process ran to completion and I was able to ‘make’ and ‘sudo
install’ and I am able to run QTGUI Widgets on the native GRC

So now the issue is seeing if I can get the cross compilation going …

Hope this saves someone some time … Chris, is your “Fm Broadcast
Tutorial” in the Public domain somewhere?


No prebuilt image has working PyQt, there is a fix in meta-oe master and
I am working on getting it added to dizzy, but some serious surgery was
done to the sip recipe. I need to review the changes to the sip recipe
before the dizzy maintainers will take it.

PyQwt is needed for the slider block. Long term, we want to drop the
need for PyQwt since there are support issues with PyQwt (see emails
from Tom R.).

Sorry for the slow response to this. I was buried in a very strange
issue late last week. I should have some time to work over the sip issue
blocking the dizzy update.

It occurs to me that we (as in the OpenEmbedded people) could use a web
page explaining release branches and development process to people that
are not familiar with how that project works.