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

Justin Ross commented on PROTON-808:
------------------------------------

And this, which is really a worse problem:

{noformat}
[jross@localhost flurry]$ python
Python 2.7.8 (default, Nov 10 2014, 08:19:18) 
[GCC 4.9.2 20141101 (Red Hat 4.9.2-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from proton.handlers import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib64/proton/bindings/python/proton/__init__.py", line 33, 
in <module>
    from cproton import *
  File "/usr/local/lib64/proton/bindings/python/cproton.py", line 28, in 
<module>
    _cproton = swig_import_helper()
  File "/usr/local/lib64/proton/bindings/python/cproton.py", line 24, in 
swig_import_helper
    _mod = imp.load_module('_cproton', fp, pathname, description)
ImportError: libqpid-proton.so.2: cannot open shared object file: No such file 
or directory
>>> 
[jross@localhost flurry]$ echo $PYTHONPATH
/usr/local/lib64/proton/bindings/python
{noformat}

> 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)

Reply via email to