Error with latest 3.7 build

GNU Radio
#1

Hi,

The last git pull brings me this one below; any ideas what went wrong?
Kubuntu 12.04 32bit, the pull a few days ago ran through just fine,
deleting
the build folder, cmake …, make changes nothing.

With best regards

Ralph.

[ 66%] Built target pygen_gr_pager_swig_cf5bb [ 67%] Built target
pygen_gr_pager_apps_f9137 [ 67%] Building CXX object
gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/DisplayPlot.cc.o
/home/ras/gnuradio/gr-qtgui/lib/DisplayPlot.cc:95:2: error: #else
without
#if
/home/ras/gnuradio/gr-qtgui/lib/DisplayPlot.cc:100:2: error: #endif
without
#if
/home/ras/gnuradio/gr-qtgui/lib/DisplayPlot.cc: In constructor
DisplayPlot::DisplayPlot(int, QWidget*):
/home/ras/gnuradio/gr-qtgui/lib/DisplayPlot.cc:96:18: error: class
QwtLegend has no member named setDefaultItemMode
/home/ras/gnuradio/gr-qtgui/lib/DisplayPlot.cc:96:37: error:
QwtLegendData
has not been declared
make[2]: ***
[gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/DisplayPlot.cc.o]
Error 1
make[1]: *** [gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/all] Error 2
make: *** [all] Error 2

–

Ralph A. Schmid
Mondstr. 10
90762 Frth
+49-171-3631223
[email protected]
http://www.bclog.de/

#2

On Thu, Dec 19, 2013 at 9:35 AM, Ralph A. Schmid, dk5ras
[email protected] wrote:

QwtLegend has no member named setDefaultItemMode
/home/ras/gnuradio/gr-qtgui/lib/DisplayPlot.cc:96:37: error: QwtLegendData
has not been declared
make[2]: *** [gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/DisplayPlot.cc.o]
Error 1
make[1]: *** [gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/all] Error 2
make: *** [all] Error 2

I have absolutely no clue what happened here. There was a fix on maint
to allow use of Qwt 6.1 yesterday, but somehow when I merged maint
into master, this file got corrupted. I’m looking at it now; should be
able to push a fix soon.

Tom

#3

Hi,

I have absolutely no clue what happened here. There was a fix on maint to
allow use of Qwt 6.1 yesterday, but somehow when I merged maint into
master, this file got corrupted. I’m looking at it now; should be able to
push a
fix soon.

Thank you for the fast reply - so I was not wrong in the assumption, it
should not have been my fault. No need to hurry :slight_smile:

Tom

Ralph.

#4

On Thu, Dec 19, 2013 at 9:49 AM, Ralph A. Schmid, dk5ras
[email protected] wrote:

Tom

Ralph.

Ok, pushed the fix.

Tom

#5

Ok, pushed the fix.

Everything fine now, built without further issues.

Tom

Thanks a lot!

Ralph.