qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafael H. Schloming (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-808) Binaries have their library locations stripped
Date Thu, 12 Feb 2015 19:29:13 GMT

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

Rafael H. Schloming commented on PROTON-808:
--------------------------------------------

I found a more comprehensible link about cmake and RPATH here:

    http://www.cmake.org/Wiki/CMake_RPATH_handling

I'm not quite sure what "the right" thing to do is. Based on the cmake documentation, I don't
think the stack overflow suggestion will actually fix the problem since it controls the RPATH
for stuff in the build tree which is not the same as the RPATH for stuff that is actually
installed. Note that the stack overflow question is actually about how to be able to run stuff
out of the *build* tree without using LD_LIBRARY_PATH.

> 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
>
> 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
(v6.3.4#6332)

Mime
View raw message