boost libs can't find each other in non-standard location
I'm having problems getting my boost libs to find each other on certain platforms. We're distributing the boost libs in a non-standard location. I created a runtime path in my apps that finds the boost libs fine, per ldd, but when a boost lib is dynamically liked to another boost lib in the same location it can't find it. For instance, libboost_thread needs libboost_atomic, and can't find it, even though it's in the same dir. On Linux, MacOSX and AIX, they can find each other. On Solaris and HP-UX, though, they can't. Boost version is 1_59. Strangely, we had this working with a previous version of our software on Solaris linked with Boost 1_55. I don't see the difference. I tried setting a runtime path of '.' in the boost libs themselves, but it ends up being '.' wherever I am, NOT where the lib is. -- Hugh Caley Software Developer, Rocket Aldon Rocket Software 2200 Powell Street · Suite 900 · Emeryville · CA · 94608-1809 · USA · Tel: +1.510.285.8542 Email:hcaley@rocketsoftware.commailto:Email:hcaley@rocketsoftware.com Web:http://aldon.rocketsoftware.com ================================ Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ +1 877.328.2932 ■ +1 781.577.4321 Unsubscribe From Commercial Email – unsubscribe@rocketsoftware.com Manage Your Subscription Preferences - http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_Subsc... Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.
Le 31/08/2016 à 04:16, Hugh Caley a écrit :
I'm having problems getting my boost libs to find each other on certain platforms. We're distributing the boost libs in a non-standard location. I created a runtime path in my apps that finds the boost libs fine, per ldd, but when a boost lib is dynamically liked to another boost lib in the same location it can't find it. For instance, libboost_thread needs libboost_atomic, and can't find it, even though it's in the same dir. On Linux, MacOSX and AIX, they can find each other. On Solaris and HP-UX, though, they can't.
Boost version is 1_59. Strangely, we had this working with a previous version of our software on Solaris linked with Boost 1_55. I don't see the difference.
I tried setting a runtime path of '.' in the boost libs themselves, but it ends up being '.' wherever I am, NOT where the lib is.
Hi, giving the failing command line should help others to see what is wrong. Best, Vicente
participants (2)
-
Hugh Caley
-
Vicente J. Botet Escriba