On 2025-02-04, Sandeep Gupta <gupta.sand...@gmail.com> wrote: > --000000000000558763062d4b3fc8 > Content-Type: text/plain; charset="UTF-8" > > Hello, > > I compiled and build python 3.13.1 using openSSL. Running it fails with > segfault:
You have most likely built against a mixture of openssl and libressl headers/library. You can check this by temporarily adding a #error to some common header e.g. /usr/include/openssl/ssl.h and see if it triggers. > doas egdb /var/run/www/run_unit_0/venv/bin/python3 python3.13.core btw, I wouldn't really recommend running gdb as root unless you really need to... > Reading symbols from /var/run/www/run_unit_0/venv/bin/python3... > [New process 101020] > Core was generated by `python3.13'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 _bsaes_key_convert () at crypto/aes/bsaes-armv8.S:926 > > warning: 926 crypto/aes/bsaes-armv8.S: No such file or directory > > For now I would revert to system packaged python3.12 but was wondering if > something obvious stand out maybe about what version of openSSL to use If you want to combine this with any library from packages that uses libssl/libcrypto (for example, for a compiled extension), you really need to build against libressl not openssl. You may need some of the patches from ports/lang/python/3 to get it to build with crypto support. -- Please keep replies on the mailing list.
