[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] build problem
From: |
LRK |
Subject: |
Re: [Discuss-gnuradio] build problem |
Date: |
Mon, 21 Nov 2005 16:59:32 -0600 |
User-agent: |
Mutt/1.4.2.1i |
On Mon, Nov 21, 2005 at 02:32:44PM -0800, Eric Blossom wrote:
> >
> > 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.
I ran the test_general script by hand after editing and make'ing in
src/lib. Best I could tell the tests/.libs/test_general would look in
both libraries, old one first.
1. Edit general/qa_gr_fxpt_nco.cc
2. make
3. ../tests/test_general (failed)
4. rm /usr/gr/local/lib/gnuradio*
5. ../tests/test_general (passed)
Not a problem if it works right for the normal make check. Just
thought I'd mention it.
--
LRK
address@hidden