discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] Updated of Make Test fail with Gnuradio Gentoo In


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Updated of Make Test fail with Gnuradio Gentoo Installation
Date: Sun, 13 Jan 2013 10:40:37 -0500

On Fri, Jan 11, 2013 at 4:31 PM, Tommy Tracy II <address@hidden> wrote:
Thank you; I tried that, and that was also unsuccessful.

                   Sincerely,
          Tommy James Tracy II
          PhD Student
High Performance Low Power Lab 
           University of Virginia


Tommy,

First, you don't need to worry about running ldconfig for the tests since they testing suite only uses binaries in the build tree, not the installed versions.

The problem with the filter_swig might come from a parallel build issue that we thought we licked recently. When you run make, do you do a parallel build?

Tom


 
On Jan 11, 2013, at 3:18 PM, Alexandru Csete <address@hidden> wrote:

I don't know if it has anything to do with it but I recommend that you
try to run cmake, make and make test as a regular user, not as root.
ldconfig should have no effect on the "make test" step.

Alex

On Fri, Jan 11, 2013 at 8:40 PM, Tommy Tracy II <address@hidden> wrote:
Dear Gnuradio,

I tried 'sudo ldconfig' before 'make test' but that didn't work either.
Below I will go through all of the failed test cases, and if anyone has any
suggestions, thank you in advance!

Here is a summary:
*Two failed VOLK tests
*gr_block_executor policy error
*Segmentation fault:
/root/src/gnuradio-3.6.3/build/gr-filter/lib/test-gr-filter
*Missing module name: filter_swig
*Rounding error


1 - qa_volk_test_all (Failed)

1: /root/src/gnuradio-3.6.3/volk/lib/testqa.cc(28): error in
"volk_32fc_32f_multiply_32fc_a_test": check
run_volk_tests(volk_32fc_32f_multiply_32fc_a_get_func_desc(), (void
(*)())volk_32fc_32f_multiply_32fc_a_manual,
std::string("volk_32fc_32f_multiply_32fc_a"), 1e-4, 0, 20460, 1, 0, "NULL")
== 0 failed [true != 0]

...

reply via email to

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