Bug 8789 - gnuradio make tests fail with boost-1.52
Summary: gnuradio make tests fail with boost-1.52
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Barry Jackson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 8825
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-23 12:38 CET by Barry Jackson
Modified: 2013-04-21 15:35 CEST (History)
2 users (show)

See Also:
Source RPM: gnuradio-3.6.3-3.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Barry Jackson 2013-01-23 12:38:50 CET
Description of problem:
As summary.

I have queried this issue upstream and it seems that the gnuradio developers blacklisted boost-1.52. This is not apparent during build.
It builds fine with tests disabled, which I have had to do for some time due to one test (of 180) causing build failures on the BS.
It now fails 143 of the 180 tests.

I set up a system locally using boost-1.53beta1 and re-built the one dep that uses boost (uhd) and gnuradio itself.
This build only fails on 3 tests.

I have sent the logs to gnuradio ML and pointed out that updating boost to a beta for Mga3 is not an option (??) and am awaiting comment.

We may have to drop gnuradio if this cannot be resolved upstream.

It does seem that boost-1.52 has problems.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Barry Jackson 2013-01-24 13:44:24 CET
I have had confirmation from upstream that gnuradio cannot be built with boost-1.52.
#------------------------------------------

Barry,

I'm afraid we can't use Boost 1.52 with GNU Radio. See:
https://svn.boost.org/trac/boost/ticket/7669

The thread join_all is very important for clean operation of a flowgraph. There's a similar bug in 1.47 that we can't use, either. In fact, you shouldn't have been able to compile against 1.52 since we've explicitly disabled it in GrBoost.cmake.

Is there an option of going back to 1.51?

Tom
#-----------------------------------------

They seem happy that with patching it should be OK with boost-1.53.

Currently 1.53beta1 is available, however whether moving to this would break other packages I don't know.

Severity: normal => critical

Barry Jackson 2013-01-26 14:04:29 CET

Depends on: (none) => 8825

Comment 2 Barry Jackson 2013-03-13 21:22:27 CET
boost 1.53 is now released, which fixes gnuradio.
However after a lot of test re-builds there are several packages that a change to boost-1.53 causes not to build:-

libyui
Failed: error: no type named âunspecified_bool_typeâ in âclass boost::scoped_ptr<YWidgetPrivate>â
http://mtf.no-ip.co.uk/pub/linux/barjac/boost/log.libyui

mapnik
Failed: error: invalid initialization of reference of type ââ¬Ëboost::fusion::cons<mapnik::feature_impl&, boost::fusion::nil>::car_type {aka mapnik::feature_impl&}ââ¬â¢ from expression of type ââ¬Ëconst car_type {aka const boost::error_cant_deduce_type}ââ¬â¢
http://mtf.no-ip.co.uk/pub/linux/barjac/boost/log.mapnik

vegastrike
Failed error: no matching function for call to 'boost::shared_array<char>::reset(int)â
http://mtf.no-ip.co.uk/pub/linux/barjac/boost/log.vegastrike

vigra
Failed: error: there are no arguments to âPyString_Checkâ that depend on a template parameter, so a declaration of âPyString_Checkâ must be available [-fpermissive]
http://mtf.no-ip.co.uk/pub/linux/barjac/boost/log.vigra

spring also fails to build but I don't think it's boost related.
Failed (undefined reference to `L_LOG') 
http://mtf.no-ip.co.uk/pub/linux/barjac/boost/log.spring
Comment 3 Barry Jackson 2013-03-30 21:10:44 CET
Now only failures are:
libyui
vegastrike
Comment 4 Olivier Blin 2013-03-31 21:33:54 CEST
About vegastrike, this patch could fix the issue you mentioned:
http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/vegastrike/src/networking/lowlevel/packetmem.cpp?r1=12089&r2=13530

CC: (none) => mageia

Comment 5 Sander Lepik 2013-04-21 09:24:56 CEST
Barry, can we close this bug?

CC: (none) => sander.lepik

Comment 6 Barry Jackson 2013-04-21 15:35:09 CEST
Yes - done.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.