[Boost-build] Cross-compiled boost shared objects contain long paths to other boost shared objects

Subject: [Boost-build] Cross-compiled boost shared objects contain long paths to other boost shared objects
From: Eric Wenger (eric.j.wenger_at_[hidden])
Date: 2013-05-10 12:01:52

I've followed the instructions for cross-compiling on the boost website to
cross-compile a set of ARM Linux hard-float binaries (boost 1.50) from
Windows using the Linaro windows toolchain (v4.7).  Everything works fine,
including setting a custom rpath for our system, but I cannot resolve the
following issue.  If I use objdump -p <boost.so> it shows the following
NEEDED line:

Dynamic Section:
  NEEDED
bin.v2\libs\system\build\gcc-arm\release\target-os-linux\threadapi-pthread\threading-multi\libboost_system-gcc-mt-1_50.so.1.50.0
  NEEDED               librt.so.1
  NEEDED               libstdc++.so.6
  NEEDED               libm.so.6
  NEEDED               libgcc_s.so.1
  NEEDED               libpthread.so.0
  NEEDED               libc.so.6

No matter what the rpath is, it always looks for the full path to the
required object which doesn't exist on my target.  Any ideas how I can
resolve this?

Thanks,
Eric