Problem with libtool while making the gnuradio 3.5

GNU Radio
1

Hi All,

I was trying to install gnuradio 3.5.

I used this command to install dependencies

sudo apt-get -y install git-core autoconf automake libtool g++
python-dev
swig pkg-config libboost-all-dev libfftw3-dev libcppunit-dev libgsl0-dev
libusb-dev sdcc libsdl1.2-dev python-wxgtk2.8 python-numpy
python-cheetah
python-lxml doxygen python-qt4 python-qwt5-qt4 libxi-dev
libqt4-opengl-dev
libqwt5-qt4-dev libfontconfig1-dev libxrender-dev

And then followed following
./bootstrap
Success
./configure --with-boost=$BOOST_PREFIX
Success
make
Following Error:
Entering directory `/home/himanshu/gnuradio-3.5.0/gruel/src/lib/pmt’
/bin/bash …/…/…/…/libtool --tag=CXX --mode=compile g++
-DHAVE_CONFIG_H -I. -I…/…/…/…
-I/home/himanshu/gnuradio-3.5.0/gruel/src/include
-I/home/himanshu/gnuradio-3.5.0/gruel/src/include -I/usr/include -g
-O2
-Wall -Woverloaded-virtual -pthread -MT pmt.lo -MD -MP -MF
.deps/pmt.Tpo
-c -o pmt.lo pmt.cc
libtool: Version mismatch error. This is libtool 2.4
Debian-2.4-2ubuntu1,
but the
libtool: definition of this LT_INIT comes from libtool 2.2.6b.
libtool: You should recreate aclocal.m4 with macros from libtool 2.4
Debian-2.4-2ubuntu1
libtool: and run autoconf again.
make[8]: *** [pmt.lo] Error 63

Thanks

Shashank

2

so I tried following and now have this error

$ rm aclocal.m4
$ aclocal
$ autoconf
$ ./configure
Error:
checking for CPPUNIT… yes
./configure: line 13863: syntax error near unexpected token 1.37' ./configure: line 13863: AX_BOOST_BASE(1.37)’

Last time there were no error for ./configure but this time there is
this
error. What should I do?

Thank you for inputs

Shashank

3

On Mon, Jul 22, 2013 at 4:52 PM, Shashank G. [email protected]
wrote:

Last time there were no error for ./configure but this time there is this
error. What should I do?

Thank you for inputs

Shashank

Why are you trying to build 3.5?

Tom

4

On Tue, Jul 23, 2013 at 2:33 PM, Shashank G. [email protected]
wrote:

./configure: line 13863: syntax error near unexpected token `1.37’
Why are you trying to build 3.5?
Shashank

I was trying to install gnuradio 3.5.
./bootstrap
-Wall -Woverloaded-virtual -pthread -MT pmt.lo -MD -MP -MF .deps/pmt.Tpo -c

Shashank

Ok.

3.5 should work. I just build 3.5.3.2 on my machine here. Try using
cmake instead of autotools, though. We’ve been keeping up to date with
cmake. Not sure what version of autotools might cause problems at this
point.

Tom

5

Ok.

3.5 should work. I just build 3.5.3.2 on my machine here. Try using
cmake instead of autotools, though. We’ve been keeping up to date with
cmake. Not sure what version of autotools might cause problems at this
point.

Tom

Thanks a lot, I also build same version as you and it was pretty easy.
But somehow I am having another error from swig while doing the make
of the modified OOT module.

/usr/local/include/gnuradio/swig/gnuradio.i:28: Error: Unable to find
‘gruel_common.i’

Now this file is in the path /usr/local/include/gruel/swig, which I
tried to include inside the Makefile.common as following:

STD_DEFINES_AND_INCLUDES =
$(DEFINES)
-I$(GNURADIO_CORE_INCLUDEDIR)
-I$(GNURADIO_CORE_INCLUDEDIR)/swig
-I/usr/local/include/gruel/swig

and I am not sure if it worked. But “make” went on to errors inside
the c++ files where I had done some changes. So just to be sure I also
tried (on the same machine) to install original OOT module, and had
the same error again.

/usr/local/include/gnuradio/swig/gnuradio.i:28: Error: Unable to find
'gruel_common.i

Now when this time I tried to make changes in Makefile.common, it
doesnt work. Any ideas about that?

Thanks

6

Ok, So that means I just need to keep my eyes open. Will try it again
tonight.

Shashank

7

On Tue, Jul 23, 2013 at 10:12 PM, Shashank G. [email protected]
wrote:

Thanks a lot, I also build same version as you and it was pretty easy.
$(DEFINES)
'gruel_common.i

Now when this time I tried to make changes in Makefile.common, it
doesnt work. Any ideas about that?

Thanks

Shashank,

You’re on the right path. Just try again and be careful about things.
This issue was discussed in a previous thread, which might shed some
light on things:

http://lists.gnu.org/archive/html/discuss-gnuradio/2012-04/msg00355.html

Tom