[jira] [Commented] (PROTON-958) [python] pip installed binding fails to find correct libqpid-proton.so
[ https://issues.apache.org/jira/browse/PROTON-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642955#comment-14642955 ] ASF subversion and git services commented on PROTON-958: Commit 4b306ad435797e0cdd0fa8a8c1ad80736bbe6825 in qpid-proton's branch refs/heads/master from [~kgiusti] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4b306ad ] PROTON-958: fix stale RPATH in python binding extension _cproton.so When the python binding is installed on a system that does not have libqpid-proton installed, pull down the Proton C sources and build them into the extension. > [python] pip installed binding fails to find correct libqpid-proton.so > -- > > Key: PROTON-958 > URL: https://issues.apache.org/jira/browse/PROTON-958 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.10 > > > The latest versions of pip keeps a cache of downloaded packages. It also > caches the results of any extensions built for those packages. When a user > tries to re-install (or install in a different virtualenv) a previously build > package, the pre-built package is pulled from the cache and plopped into > place. > Which is all great and fast... > ... unless your extension also builds a shared library (libqpid-proton) and > sets its RPATH to it. > This ends up with a cached _cproton.so with a RPATH pointing to the directory > where the libqpid-proton.so was installed. Woe be you if that was a > virtualenv that you deleted (or updated). > This results in either "libqpid-proton.so not found" errors when importing > the bindings, or symbol mismatches if the library was overwritten. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-958) [python] pip installed binding fails to find correct libqpid-proton.so
[ https://issues.apache.org/jira/browse/PROTON-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642956#comment-14642956 ] ASF subversion and git services commented on PROTON-958: Commit 343d742f50e295751ac9822384bf5acd4abd0093 in qpid-proton's branch refs/heads/master from [~kgiusti] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=343d742 ] Merge branch 'master' into PROTON-958 > [python] pip installed binding fails to find correct libqpid-proton.so > -- > > Key: PROTON-958 > URL: https://issues.apache.org/jira/browse/PROTON-958 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.10 > > > The latest versions of pip keeps a cache of downloaded packages. It also > caches the results of any extensions built for those packages. When a user > tries to re-install (or install in a different virtualenv) a previously build > package, the pre-built package is pulled from the cache and plopped into > place. > Which is all great and fast... > ... unless your extension also builds a shared library (libqpid-proton) and > sets its RPATH to it. > This ends up with a cached _cproton.so with a RPATH pointing to the directory > where the libqpid-proton.so was installed. Woe be you if that was a > virtualenv that you deleted (or updated). > This results in either "libqpid-proton.so not found" errors when importing > the bindings, or symbol mismatches if the library was overwritten. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-958) [python] pip installed binding fails to find correct libqpid-proton.so
[ https://issues.apache.org/jira/browse/PROTON-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639440#comment-14639440 ] Ken Giusti commented on PROTON-958: --- Reviewboard link: https://reviews.apache.org/r/36744/ > [python] pip installed binding fails to find correct libqpid-proton.so > -- > > Key: PROTON-958 > URL: https://issues.apache.org/jira/browse/PROTON-958 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.10 > > > The latest versions of pip keeps a cache of downloaded packages. It also > caches the results of any extensions built for those packages. When a user > tries to re-install (or install in a different virtualenv) a previously build > package, the pre-built package is pulled from the cache and plopped into > place. > Which is all great and fast... > ... unless your extension also builds a shared library (libqpid-proton) and > sets its RPATH to it. > This ends up with a cached _cproton.so with a RPATH pointing to the directory > where the libqpid-proton.so was installed. Woe be you if that was a > virtualenv that you deleted (or updated). > This results in either "libqpid-proton.so not found" errors when importing > the bindings, or symbol mismatches if the library was overwritten. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
