Boost logo

Boost-Build :

Subject: [Boost-build] boost python examples do not always build
From: Avi Bahra (avibahra_at_[hidden])
Date: 2010-04-23 06:28:56

Depending on the platform the boost python examples do not
always build.
On Linux (gcc/boost1.42) this is not an issue. If we compile
This builds a shared library

ldd bin/gcc-4.2.1/debug/ => (0xffffe000) =>
(0xb7e7e000) => /lib/ (0xb7e58000) => /lib/ (0xb7e40000) => /lib/ (0xb7e3c000) =>
(0xb7d4e000) => /lib/ (0xb7d29000) =>
(0xb7d1d000) => /lib/ (0xb7be9000)
        /lib/ (0x80000000)

It can be seen that libutil, libpthread,libstdc , etc, get implicitly
Its not clear if this controlled by python-extension rule, or ldconfig
or bjam rules for building shared libs ?

However on HPUX(aCC/boost 1.42), the equivalent libs for
aCC compiler do not get linked, as a result the examples fail
during the import step, due to unresolved symbols.

For my app, currently I am using python-extension rule in my jamfile,
and hence suffer the same problems.
Is there a way for me change python-extension rule , so
that the additional std libs on HPUX get pulled in ?

If not, is there any way, hacky or not, of conditionally adding
the libs for HPUX only. i.e _equivalent_ to:

#ifdef LINUX
lib pthread ;
python-extension ecf_ext : [ glob src/*.cpp ]
           : <variant>debug:<define>DEBUG

#ifdef HPUX
lib pthread ;
lib std_v2 ;
lib stream ;
lib Csup ;
lib unwind ;
lib m ;
python-extension ecf_ext : [ glob src/*.cpp ]
           : <variant>debug:<define>DEBUG

Any help appreciated.

  Best regards,

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at