[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] Build from CVS fails, tarball succeeds, at _gnuradio_

From: Jonathan Jacky
Subject: [Discuss-gnuradio] Build from CVS fails, tarball succeeds, at _gnuradio_swig_python.la
Date: Fri, 13 May 2005 17:49:16 -0700 (PDT)

I've succesfully built gnuradio-core-2.5 from the tarball.
I tried building from CVS for the first time today and failed. In particular, make fails at the command to create _gnuradio_swig_python.la

I'm using Mac OS X 10.3.8 "Panther" with autoconf 2.59, automake 1.9.4,
pkg-config 0.15.0, libtool 1.5.2, and swig 1.3.24.

I built gnuradio-core-2.5 from the tarball again and compared all the
messages to the build from CVS to identify the point where they
differ.  Here's what I found.

bootstrap - no differences

configure - build from 2.5 tarball does not check for Python library path.
            build from CVS checks for Python library path, can't find it,
             issues warning (this doesn't seem to be related to the failure)

make - In make, the two builds behave identically up through here:
Making all in swig
mkdir .libs
 g++ ...  -o .libs/gnuradio_swig_python.o

Then they differ.  Building from the 2.5 tarball:

/bin/sh ../../../libtool ...  -o _gnuradio_swig_python.la
... -avoid-version gnuradio_swig_python.lo ...

Building from CVS, there is one more flag, -no-undefined:

/bin/sh ../../../libtool ... -o _gnuradio_swig_python.la ... -avoid-version -no-undefined gnuradio_swig_python.lo ...

And then, building _gnuradio_swig_python.la from the 2.5 tarball succeeds:

g++ -Wl,-bind_at_load -flat_namespace -undefined suppress
-o .libs/_gnuradio_swig_python.dylib
-bundle  .libs/gnuradio_swig_python.o
-L/opt/local/lib ../../../src/lib/.libs/libgnuradio-core.dylib
/opt/local/lib/libcppunit.dylib -lstdc++
creating _gnuradio_swig_python.la

But building it from CVS it fails, and the command that fails is different:

g++ -Wl,-bind_at_load
-o .libs/_gnuradio_swig_python.so
-bundle .libs/gnuradio_swig_python.o /opt/local/lib/libcppunit.dylib -L/opt/local/lib ../../../src/lib/.libs/libgnuradio-core.dylib
ld: Undefined symbols:
... (many many more undefined symbols)
make[5]: *** [_gnuradio_swig_python.la] Error 1

(I wrapped the lines above so they'd fit, and to ease comparison)

I find that all the undefined symbols are there in
as revealed by
 % nm gnuradio_swig_python.o | grep _Py

I also diff'ed Makefile.in, Makefile.am and Makefile (in swig) in the
two versions and found differences consistent with the differences in
the commands, but I don't know how to interpret them.

Any suggestions about what I should do to build from CVS?

Jon Jacky

reply via email to

[Prev in Thread] Current Thread [Next in Thread]