$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: rwgk_at_[hidden]
Date: 2001-10-24 11:30:34
--- In boost_at_y..., "David Abrahams" <david.abrahams_at_r...> wrote:
>
> ----- Original Message -----
> From: <boost_at_c...>
>
> > Hi-
> > I am trying to get Boost working on my PC - RH7.1, GCC 2.96,
> > python1.5.2, boost 1.25.0. I tried to build the getting_started1
> > example, but I get the following error when I try to import the
> > module:
> >
> > >>> import getting_started1
> > Traceback (most recent call last):
> > File "<stdin>", line 1, in ?
> > ImportError: ./getting_started1.so: undefined symbol:
> > __Q35boost6python14module_builderPCc
> >
> > Here is my makefile output:
> > g++ -I/usr/local/packages/boost_1_25_0/ -I/usr/include/python1.5
> > -c -o getting_started1.o getting_started1.C
> > ld -shared -o getting_started1.so getting_started1.o
>
> I can't say much about the make system, but maybe Ralf can
> comment...
This certainly is not the output of the makefile that is
provided in the boost/libs/python/build directory. The
ld commands fails to link against all the support *.o,
or alternatively the libboost_python.a file.
I have successfully built Boost.Python with linux_gcc.mak
under RH 7.1 with the gcc 2.96 compiler. However, the tests
fail at runtime b/o the notorious exception handling bugs.
Next I have tried gcc 2.95.3. Same problem (which is interesting,
because gcc 2.95.3 works under RH 6.1). The only compiler
that works both at compile-time and at runtime under RH 7.1 is
gcc 3.0 (you can ignore the long list of bogus warnings when
compiling some of the richcmp?.cpp tests).
Ralf