[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695989#comment-14695989
]
Andrew Stitcher commented on PROTON-952:
----------------------------------------
It may be a "cmake bug" in that cmake doesn't ensure that it uses the same
version for both python and python library. But it is straightforward to solve
in the proton cmake files.
> Building Proton with python 2.6 and python 3.4 on Travis CI finds and links
> wrong libpython
> -------------------------------------------------------------------------------------------
>
> Key: PROTON-952
> URL: https://issues.apache.org/jira/browse/PROTON-952
> Project: Qpid Proton
> Issue Type: Bug
> Affects Versions: 0.10
> Environment: Travis CI build environment (highly customised Ubuntu)
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Fix For: 0.11
>
>
> You can specify a specifiv version of python to use in the Traviis build
> process and that will set up the build environment to use a python virtualenv
> with that version of python.
> When using python 2.6 or 3.4 (and probably 3.3 too but I've not tested that)
> the cmake installed will find the python 2.7 libs and link them into the
> proton bindings extension. This seems to succeed at build time but seems to
> make the "python-test" fail to even start in both cases (though with slightly
> different symptoms).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
