You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2015/02/12 20:21:11 UTC
[jira] [Commented] (PROTON-808) Binaries have their library
locations stripped
[ https://issues.apache.org/jira/browse/PROTON-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318808#comment-14318808 ]
Andrew Stitcher commented on PROTON-808:
----------------------------------------
The stack overflow "discussion" is somewhat incomprehensible to me - could you be specific about what you want to change to solve this problem?
Will it also fix the problem in the previous comment? Perhaps that is a separate issue?
I think what you are suggesting is that there are bugs in cmake and in python that we need to work around - is that the case?
> 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)