Re: [Boost-build] AIX hardcodes paths shared libs with generated link command

From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-06-28 05:33:07

On Friday 27 June 2008 13:15:23 Andrej van der Zee wrote:

Hi Andrej,

[CC for convenience, please reply on-list]

> 
> I am having some problems linking on AIX with bjam
> using toolset=gcc. In my project I have one executable
> and one shared lib. Bjam generates the following
> linker command for the executable:
> 
> "g++" -o <all-object-files>
> "../util/bin/gcc-4.2.4/debug/threading-multi/libspeedo_util.so"
>  -lrt  -g -Wl,-brtl -pthread
> -Wl,-blibpath:/usr/lib/:/speedo/lib:/usr/local/lib
> 
> Now this results in an executable that does NOT look
> for libspeedo_util.so in any other directories than
> the relative path
> ../util/bin/gcc-4.2.4/debug/threading-multi! 
> 
> This is clearly not what I want. 

Here's the code that affects this:

if [ os.name ] != NT && [ os.name ] != OSF && [ os.name ] != HPUX && [ os.name ] != AIX
{
    # OSF does have an option called -soname but it doesn't seem to work as
    # expected, therefore it has been disabled.
    HAVE_SONAME   = "" ;
    SONAME_OPTION = -h ;
}

Does commenting out the check for AIX make things work?

- Volodya