[
https://issues.apache.org/jira/browse/PROTON-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921477#comment-16921477
]
Andrew Stitcher commented on PROTON-2097:
-----------------------------------------
* To see the full CMake configure output you need to run CMake with no cache -
I think you have run CMake before in this directory so there is a cache present.
* The SYSINSTALL_PYTHON=ON option is a hold over for a time long ago, and is
not much used or tested currently, so this may be an issue - you shouldn't need
it.
* Your error looks like a issue with the LD_LIBRARY_PATH - does pyenv set one
up? If so does it actually point to the place where libcrypto.so actually is?
One thing to try is finding the _cproton.so that is built as the loadable
python extension (it may have a longer name like
_cproton.cpython-37m-x86_64-linux-gnu.so) and running {{ldd _cproton....so}}
> Linkage error when openssl version is too old or new (not sure)
> ---------------------------------------------------------------
>
> Key: PROTON-2097
> URL: https://issues.apache.org/jira/browse/PROTON-2097
> Project: Qpid Proton
> Issue Type: Improvement
> Components: python-binding
> Affects Versions: proton-c-0.29.0
> Reporter: Omer Katz
> Priority: Major
> Fix For: proton-c-0.30.0
>
>
> After successfully building I'm getting the following error when I try to
> import _cproton.
> {code:java}
> undefined symbol: CRYPTO_set_locking_callback{code}
> This is not the behavior I expected.
> The build should fail if this symbol is not present.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
