[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Install: qa_volk_test_all fails on armv7
From: |
Tom Rondeau |
Subject: |
Re: [Discuss-gnuradio] Install: qa_volk_test_all fails on armv7 |
Date: |
Tue, 26 Nov 2013 11:41:00 -0500 |
On Tue, Nov 26, 2013 at 10:38 AM, Ken Adams <address@hidden> wrote:
> The volk test is failing on my gnuradio build on a Beaglebone Black (armv7h)
> running Arch Linux Arm.
>
> Configuration that failed to enable:
> gr-ctrlport *** disabled [do i need this?]
> gr-comedi *** disabled [don't need]
> gr-qtgui *** disabled [don't need]
> gr-documentation *** disabled [don't need]
>
>
> # make test
> start 1: qa_volk_test_all
> *** 2 failures detected in test suite "Master Test Suite"1/177 Test #1:
> qa_volk_test_all .....................***Failed 9.88 sec
>
> # ctest -V -R qa_volk_test_all | grep error
>
> 1: /root/build/gnuradio-git/src/gnuradio/volk/lib/testqa.cc(10): error in
> "volk_16ic_s32f_deinterleave_32f_x2_test": check
> run_volk_tests(volk_16ic_s32f_deinterleave_32f_x2_get_func_desc(), (void
> (*)())volk_16ic_s32f_deinterleave_32f_x2_manual,
> std::string("volk_16ic_s32f_deinterleave_32f_x2"), 1e-4, 32768.0, 20462, 1,
> 0, "NULL") == 0 failed [true != 0]
>
> 1: /root/build/gnuradio-git/src/gnuradio/volk/lib/testqa.cc(39): error in
> "volk_32fc_s32f_magnitude_16i_test": check
> run_volk_tests(volk_32fc_s32f_magnitude_16i_get_func_desc(), (void
> (*)())volk_32fc_s32f_magnitude_16i_manual,
> std::string("volk_32fc_s32f_magnitude_16i"), 1, 32768, 20462, 1, 0, "NULL")
> == 0 failed [true != 0]
>
> Full output of ctest -V _R qa_volk_test_all is attatched.
>
> I'm not really sure how to go from here to diagnose the problem. I'm
> building the latest gnuradio git source (packaged by the AUR) on the beagle
> bone black via distcc which is cross compiling on my x86_64 desktop with the
> same toolchain.
>
> Any advice?
>
> As far as configuration these failed to get enabled:
which version of GNU Radio? These bugs were fixed on Nov. 19 and will
be a part of the 3.7.2.1 release. See bugs #582 and #583 on our Issues
page.
Tom