discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Tests fail building with boost1.52


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Tests fail building with boost1.52
Date: Thu, 24 Jan 2013 09:28:13 -0500

On Thu, Jan 24, 2013 at 7:42 AM, Barry Jackson <address@hidden> wrote:
On 23/01/13 15:05, Tom Rondeau wrote:
On Wed, Jan 23, 2013 at 9:58 AM, Philip Balister <address@hidden
<mailto:address@hidden>> wrote:

    On 01/23/2013 09:45 AM, Tom Rondeau wrote:
     > On Wed, Jan 23, 2013 at 5:42 AM, Barry Jackson
    <address@hidden <mailto:address@hidden>> wrote:
     >
     >> I package gnuradio for Mageia and we are having problems with test
     >> failures with 3.6.3 in our beta2 distro release.
     >> (from git tag v3.6.3 since release tarball was from 3.6.4git)
     >>
     >> We have boost-1.52 and the package builds, but fails 143 tests.
    Full build
     >> system log is here:-
     >> http://pkgsubmit.mageia.org/**uploads/failure/cauldron/core/**
     >> release/20130123090056.barjac.**valstar.22658/log/botcmd.**
     >>
    1358931665.ecosse.log<http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130123090056.barjac.valstar.22658/log/botcmd.1358931665.ecosse.log>
     >>
     >> As a test I set up a local system using boost-1.53 beta1. (with
    uhd also
     >> built on the same system)
     >> This fails only 3 tests. log is here:
     >>
    http://mtf.no-ip.co.uk/pub/**linux/barjac/soft/log.gnuradio<http://mtf.no-ip.co.uk/pub/linux/barjac/soft/log.gnuradio>
     >>
     >> Switching to boost-1.53 beta1 for us is not an option for a stable
     >> release, plus we are now in version freeze.
     >>
     >> Unless there is a fix for this using boost-1.52 then our only
    option may
     >> be to drop gnuradio from the distro.
     >>
     >> Any help will be appreciated.
     >>
     >> Barry
     >>
     >
     > 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.

    Has this been reported to the boost people? There is a boost 1.53 beta,
    I wonder if the problem is fixed there.


The link that I posted is to the Boost issue tracking system, so yes, it
has been reported :)

The ticket is closed as fixed, so it looks like 1.53 will work.

    Are the test failures related to the thread join_all problem?

    Philip

The test failures probably aren't related to this. This bug shows up by
locking the entire program on exit, so the test would never complete.
The failures are probably due to some mismatch in library versions or
pre-built code. As I said, we don't allow GNU Radio to build with 1.52,
so my guess it that cmake actually failed, but the Makefiles were still
there from previous build attempts.

Tom


I really don't know why the 1.52 build did not fail (without the tests). Our build system uses a clean minimal installation in chroot with only buildrequires installed, so nothing from previous builds can be left around.

Strange. Cmake should fail with Boost not found.
 
It was only a chance comment on irc that drew my attention to a possible problem.

Using boost 1.53b1 (with or without the gruel/thread.h patch posted earlier) in a local build I see:
          1 - qa_volk_test_all (Failed)
        115 - qa_ctcss_squelch (Failed)
        152 - qa_qtgui (Failed)

Any clues as to the cause of these?

Barry

Could you run 'ctest -V -R <test name>' for these tests to see what they are? I wouldn't worry too much about the ctcss and qtgui failures. My OSX box has a problem with ctcss, too, though I've not gone to track it down since it's not a heavily used blocks. The qtgui is probably failing due to an issue with X. This will fail for me over ssh if I don't set things up correctly.

The volk test is the most troubling, though. We definitely want that to pass. What's your processor?

Tom


reply via email to

[Prev in Thread] Current Thread [Next in Thread]