Re: [boost] unresolved external symbols with Boost Python on linux

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-11 19:43:51

How are you doing your link? Are you using Boost.Build or are you trying to
make it work yourself? I ask because it appears to be looking for the
virtual table for std::runtime_error, which would happen if you didn't have
the appropriate libraries in the link command-line for your
platform/compiler. If you're trying to link things  yourself, I suggest you
use Boost.Build. If you're using Boost.Build, I suggest you inspect the
command-lines it's using to see if something looks inappropriate to your
platform.

-Dave

----- Original Message -----
From: "Aaron Brashears" <gila_at_[hidden]>
To: "Boost" <boost_at_[hidden]>
Sent: Monday, February 11, 2002 7:19 PM
Subject: [boost] unresolved external symbols with Boost Python on linux

> Hi again. I build the boost libraries, and built getting_started1
> against the static boost libraries. Everything builds fine, and the
> .so file is enormous (as expected), but when I try to import it into
> python, I get the following error:
>
> Traceback (innermost last):
>   File "<stdin>", line 1, in ?
> ImportError: ./getting_started1.so: undefined symbol: __vt_13runtime_error
>
>
> I checked the symbol table:
>
> $ nm getting_started1.so | grep runtime_error
> 0007b928 W _._13runtime_error
> 0007b970 W __13runtime_errorRC13runtime_error
>          U
__13runtime_errorRCt12basic_string3ZcZt18string_char_traits1ZcZt24__default_
alloc_template2b1i0
>          U __vt_13runtime_error
>
>
> As you can see, the __vt_13runtime_error symbol is in fact available
> in the symbol table in some form. Does anyone know what might be going
> wrong?
>
>
>
>
> Info: http://www.boost.org  Send unsubscribe requests to:
<mailto:boost-unsubscribe_at_[hidden]>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>