Re: [Discuss-gnuradio] Build errors

[Eric Blossom]

On Wed, Jan 17, 2007 at 05:45:33PM -0500, Illix wrote:
> I'm getting the same problem (as far as I can tell) on an Ubuntu
> 6.10machine.  The build fails with undefined references in
> libmblock.so and libmblock-qa.so.
> 


OK, I've looked at the log file that Bob sent me and compared it to
what I see on my machines.  The difference appears to be something in
libtool.

My machine (works):

/bin/sh ../../../libtool --tag=CXX --mode=link g++ -g -O2 -Wall 
-Woverloaded-virtual -pthread   -o test_mblock  test_mblock.o libmblock-qa.la 
libmblock.la 
g++ -g -O2 -Wall -Woverloaded-virtual -pthread -o .libs/test_mblock 
test_mblock.o  ./.libs/libmblock-qa.so 
/home/eb/gr/trunk/mblock/src/lib/.libs/libmblock.so /usr/lib/libcppunit.so -ldl 
./.libs/libmblock.so /home/eb/gr/trunk/pmt/src/lib/.libs/libpmt.so 
/usr/lib/libstdc++.so


Bob's machine (doesn't work):

/bin/bash ../../../libtool --tag=CXX --mode=link g++ -g -O2 -Wall 
-Woverloaded-virtual -pthread   -o test_mblock  test_mblock.o libmblock-qa.la 
libmblock.la 
g++ -g -O2 -Wall -Woverloaded-virtual -pthread -o .libs/test_mblock 
test_mblock.o  ./.libs/libmblock-qa.so ./.libs/libmblock.so -Wl,--rpath 
-Wl,/usr/local/lib


Although they both make the same call to libtool, libtool spits out a
different command line on the two systems.  On Bob's (and I assume
Illix's) machine, the output of libtool contains --rpath (pointing to
the install, not build directory!), whereas my machine lists the
actual paths needed to find the pieces.

Bob's machine is using 

  ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 
22:14:06)

I'm using (SuSE 10.1)

  ltmain.sh (GNU libtool) 1.5.22 (1.1220.2.365 2005/12/18 22:14:06)

It looks like the Debian folks may have applied some kind of a patch to
libtool 1.5.22 that could be causing the problem.

Can any debian/ubuntu users figure out the difference?  That is,
what's the debian/ubuntu patch, and when and why was it applied?

Thanks,
Eric