fails to run about python-mbedtls

[Synss]

Do you really need Python 3.6? It has reached its end of life a few month ago already.

I would recommend upgrading to a supported version of Python and install a wheel. This is the easiest way and there are manylinux1 and manylinux10 wheels available.

Anyway, if mbedtls is not in the standard paths such as /usr/lib or maybe /usr/local/lib, you will need to set and export LD_LIBRARY_PATH accordingly.

[folkertvanheusden]

Hi Mathias, Python 3.6 is still the latest version in centos 7 (CentOS Linux release 7.9.2009 (Core)), that's why a wheel is not possible right now. mbedtls *is* in the path: $ ls /usr/local/lib libdmalloc.a libdmallocth.a *libmbedcrypto.a libmbedtls.a libmbedx509.a* python3.6 $ ld --verbose | grep SEARCH_DIR SEARCH_DIR("=/usr/x86_64-redhat-linux/lib64"); SEARCH_DIR("=/usr/lib64"); SEARCH_DIR("=/usr/local/lib64"); SEARCH_DIR("=/lib64"); SEARCH_DIR("=/usr/x86_64-redhat-linux/lib"); *SEARCH_DIR("=/usr/local/lib");* SEARCH_DIR("=/lib"); SEARCH_DIR("=/usr/lib"); Also: from ._tls import ( ImportError: /usr/local/lib64/python3.6/site-packages/mbedtls/_ tls.cpython-36m-x86_64-linux-gnu.so: undefined symbol: mbedtls_cipher_set_padding_mode I believe it *can* find the/a library, but the mbedtls_cipher_set_padding_mode symbol is not in it.

…

On Wed, Apr 6, 2022 at 7:01 PM Mathias Laurin ***@***.***> wrote: Do you really need Python 3.6? It has reached its end of life <https://peps.python.org/pep-0494/> a few month ago already. I would recommend upgrading to a supported version of Python and install a wheel <https://pypi.org/project/python-mbedtls/#files>. This is the easiest way and there are manylinux1 and manylinux10 wheels available. Anyway, if mbedtls is not in the standard paths such as /usr/lib or maybe /usr/local/lib, you will need to set and export LD_LIBRARY_PATH accordingly. — Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUN5IW4OQCWZUQ634NEHS43VDW7ORANCNFSM5SVIQKUA> . You are receiving this because you authored the thread.Message ID: ***@***.***>