Re: [Discuss-gnuradio] Build problem (from SVN)

[matt . nottingham]

Eric Blossom writes:
 > On Mon, May 28, 2007 at 06:52:23PM +0100, address@hidden wrote:
 > > address@hidden writes:
 > >  > Eric Blossom writes:
 > >  >  > On Mon, May 28, 2007 at 10:15:35AM +0100, address@hidden wrote:
 > >  >  > > 
 > >  >  > > Hi,
 > >  >  > > 
 > >  >  > > I don't seem able to build GnuRadio. I hecked out a copy from SVN
 > >  >  > > today and after ./bootstrap, ./configure and then make it fails 
 > > with:
 > >  >  > > [SNIP]

 > >  >  > > make[5]: *** [test_mblock] Error 1
 > >  >  > > make[5]: Leaving directory `/home/matt/gnuradio/mblock/src/lib'
 > >  >  > > make[4]: *** [all] Error 2
 > >  >  > > make[4]: Leaving directory `/home/matt/gnuradio/mblock/src/lib'
 > >  >  > > make[3]: *** [all-recursive] Error 1
 > >  >  > > make[3]: Leaving directory `/home/matt/gnuradio/mblock/src'
 > >  >  > > make[2]: *** [all-recursive] Error 1
 > >  >  > > make[2]: Leaving directory `/home/matt/gnuradio/mblock'
 > >  >  > > make[1]: *** [all-recursive] Error 1
 > >  >  > > make[1]: Leaving directory `/home/matt/gnuradio'
 > >  >  > > make: *** [all] Error 2
 > >  >  > > 
 > >  >  > > 
 > >  >  > > I'm running debian unstable on AMD64. I'm sure I had this problem
 > >  >  > > before, and it was due to the build process using old incs & libs 
 > > from
 > >  >  > > a old version I had laying around in /usr/local - but I've cleaned
 > >  >  > > /usr/local out of all old GNUradio files and it still bombs out. 
 > >  >  > > 
 > >  >  > > I'm using version 1.34.0 of boost.
 > >  >  > > 
 > >  > Eric,
 > >  > 
 > >  > Thanks for that.
 > >  > 
 > >  > I added /usr/local/lib to my ld.so.conf and did a ldconfig. Then did
 > >  > make clean and then make. Unfortunately the compilation bombed out
 > >  > again with the same error.
 > >  > 
 > >  > I'll check out a fresh copy and reconfigure it again and see if that
 > >  > helps.
 > >  > 
 > >  > Thanks,
 > >  > 
 > >  > Matt
 > > 
 > > Just to confirm that a new checkout and configure did not help.
 > > 
 > > Any other suggestions?
 > > 
 > > Thanks,
 > > 
 > > Matt
 > 
 > Try adding /usr/local/lib64 to ld.so.conf in addition to
 > /usr/local/lib, then run ldconfig.
 > 
 > Eric

Eric,

OK, I tried that - but I still get the same error message. I don't
understand why this should work - no libraries have been installed to
/usr/local yet, so why do I need to alter the ldconfig path? (Or is
this a strange 'feature' of libtool?)

Thanks again for all your help,

Matt