Hi Don, Here is the what was displayed earlier, exactly when the error occured. When I ran "make check" a couple of times afterward (one after the other), eventually it passed without any errors
Best regards, -Vijay ---------------------------------- ====================================================================== ERROR: test_002_ (__main__.qa_classify) ---------------------------------------------------------------------- Traceback (most recent call last): File "./qa_classify.py", line 94, in test_002_ self.tb.run() File "/home/Vijay/gnuradio-3.3.0/gnuradio-core/src/python/gnuradio/gr/top_bloc k.py", line 104, in run self.wait() File "/home/Vijay/gnuradio-3.3.0/gnuradio-core/src/python/gnuradio/gr/top_bloc k.py", line 107, in wait _top_block_waiter(self._tb).wait() File "/home/Vijay/gnuradio-3.3.0/gnuradio-core/src/python/gnuradio/gr/top_bloc k.py", line 59, in __init__ self.event = _threading.Event() File "/usr/lib/python2.6/threading.py", line 360, in Event return _Event(*args, **kwargs) File "/usr/lib/python2.6/threading.py", line 368, in __init__ self.__cond = Condition(Lock()) error: can't allocate lock --- On Sun, 3/6/11, Don Ward <don2387w...@sprynet.com> wrote: From: Don Ward <don2387w...@sprynet.com> Subject: Re: [Discuss-gnuradio] libstdc++ error on Cygwin To: discuss-gnuradio@gnu.org Date: Sunday, March 6, 2011, 8:34 PM Vijay Pillai wrote: > Something that I want to note was that after running "make check" > I did get an error message but the program did not halt when it > showed the error. This error did not prevent the tone so maybe it > does not matter. For reference, I am attaching the error message > at the end of this mail. [...] > Here is the error message at the end of running "make check" > FAIL: run_tests > ================== > 1 of 1 test failed > ================== Earlier in the output there should have been more information. The most likely problem would include the messages ...........sem_init: No error and error: can't allocate lock This is a problem in Cygwin and does not indicate a problem in your GNU Radio installation. It does not always occur, and "make check" may succeed if you run it enough times. -- Don W. _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
