Re: [Discuss-gnuradio] build problem

[Eric Blossom]

On Mon, Nov 21, 2005 at 04:21:52PM -0600, LRK wrote:
> On Mon, Nov 21, 2005 at 01:46:24PM -0800, Eric Blossom wrote:
> > 
> > I think the problem is that your "upgrade" somehow changed the default
> > maximum stack size.  The QA code is only allocating 1.6MB on the stack.
> > 
> > What does 
> > 
> >   $ ulimit -s
> > 
> > say?
> 
> 65536   (kbytes)
> 
> 
> I if'ed out the actual code so it definitely failed just allocating the
> space. Was a bit confusing trying to find this since it seems to use
> the old installed /usr/gr/local/lib/gnuradio*  libraries in preference
> to the new build in .../gnuradio-core/src/lib/.libs/gnuradio* but I don't
> know if that is a bug or a feature.

At least on GNU/Linux the test_* executables are actually shell
scripts created by libtool that set up the environment to point at
the non-installed libraries and then invoke the "real" executable that
lives under .libs.  

We handle python QA code in a similar manner, but use a different
technique.  "make check" uses the non-installed libraries in
.libs/gnuradio*.  See run_tests for the magic.  If you run the python
qa_*.py code by hand (not under make check or run_tests), it will
resolve to the installed libraries.

Eric