[ 
https://issues.apache.org/jira/browse/PROTON-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864650#comment-16864650
 ] 

Jiri Daněk edited comment on PROTON-808 at 6/15/19 10:10 AM:
-------------------------------------------------------------

I hit this problem on macOS with the Python bindings. There 
{{bindings/python/_cproton.so}} is not able to find the cproton libraries when 
I import it in python. One additional problem with macOS is that in the default 
setting, there are restrictions on {{DYLD_FALLBACK_LIBRARY_PATH}} which makes 
things awkward 
[https://github.com/conda-forge/conda-forge.github.io/issues/238.]

The only thing I could think of is the patch here, the {{set 
(CMAKE_INSTALL_RPATH ${CMAKE_INSTALL_PREFIX}/${LIB_INSTALL_DIR})}}. Reason why 
{{CMAKE_INSTALL_RPATH_USE_LINK_PATH}} does not work is because it only keeps 
rpaths that point out of the CMAKE_INSTALL_PREFIX subtree.

This problem means that I have to have a special macOS-only command to fix the 
rpath after the build,
{code:java}
install_name_tool -add_rpath $PREFIX/lib/. 
$PREFIX/lib/proton/bindings/python/_cproton.so{code}


was (Author: jdanek):
I hit this problem on macOS with the Python bindings. There 
{{bindings/python/_cproton.so}} is not able to find the cproton libraries when 
I import it in python. One additional problem with macOS is that in the default 
setting, there are restrictions on {{DYLD_FALLBACK_LIBRARY_PATH}} which makes 
things awkward 
[https://github.com/conda-forge/conda-forge.github.io/issues/238.]

The only thing I could think of is the patch here, the \{{set 
(CMAKE_INSTALL_RPATH ${CMAKE_INSTALL_PREFIX}/${LIB_INSTALL_DIR})}}. Reason why 
{{CMAKE_INSTALL_RPATH_USE_LINK_PATH}} does not work is because it only keeps 
rpaths that point out of the CMAKE_INSTALL_PREFIX subtree.

This problem means that I have to have a special macOS-only command to fix the 
rpath after the build, \{{install_name_tool -add_rpath $PREFIX/lib/. 
$PREFIX/lib/proton/bindings/python/_cproton.so}}

> Binaries have their library locations stripped
> ----------------------------------------------
>
>                 Key: PROTON-808
>                 URL: https://issues.apache.org/jira/browse/PROTON-808
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>            Reporter: Justin Ross
>            Assignee: Justin Ross
>            Priority: Major
>             Fix For: proton-c-future
>
>         Attachments: cmake.patch
>
>
> 1. Build proton
> 2. Install to /usr/local
> 3. Run "proton"
> -> Blows up, can't find its library
> https://paste.apache.org/gd56
> http://stackoverflow.com/questions/3352041/creating-binary-with-cmake-removes-runtime-path
> The default behavior of cmake is in my opinion wrong, and we should use the 
> fix mentioned in that stackoverflow discussion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to