qpid-proton mailing list archives

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

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

Justin Ross commented on PROTON-808:

No, it's about the install output.  He just happens to be installing it to his home dir. 
From the SO question:

When I run make install the program gets put in the correct place, but the cmake installer
removes the runtime path from the binary.

-- Install configuration: "Debug"
-- Installing: *binary name*
-- Removed runtime path from "*binary name*"

Andrew thinks the right thing is to require the user to update the system ld configuration
or override LD_LIBRARY_PATH.  There is apparently a security motivation for this.

> 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

View raw message