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

From: Andrej van der Zee (mavdzee_at_[hidden])
Date: 2008-07-09 21:46:47

Hi,

I still have an open issue with the generated AIX
linker command. The problem is that with the current
generated command, it hard-codes the library path in
the loader section of executables and libraries. In
Linux this is solved with -soname linker option, but
on AIX an exact same option does not exist. Though,
the AIX linker provides -bnoipath that strips the path
in the loader section of the target. Note that this
also holds for libraries; for example a boost library
that depend on another boost library (for example
boost_filesystem depends on boost_system) and that is
build without the -bnoipath option, has the relative
path (into the boost source tree) hard-coded in the
loader section (and this relative path *only* is used
when the lib is loaded upon execution).

So I think -bnoipath should be added to the AIX linker
command. An alternative would be to rewrite the
generated linker command where the relative path
prepending the library is replaced by
-L<relative-path> and the library itself is specified
as -l<libname>. But as far as I can see, this ends up
in the same entries in the loader sections of
executables and libraries. 

Cheers,
Andrej 

      __________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html