Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"
- Reply: Mark Millard : "Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC""
- In reply to: Mike Karels : "Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC""
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 10 Jul 2023 17:55:54 UTC
On Jul 10, 2023, at 09:45, Mike Karels <mike@karels.net> wrote: > On 10 Jul 2023, at 10:56, Mark Millard wrote: > >> The subject line's question was prompted by >> . . ./hazmat/bindings/_openssl.abi3.so related notices >> in a kyua report: >> >> # kyua report --verbose --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785 2>&1 | grep "Undefined symbol" | sort -u >> +ImportError: /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol "ERR_GET_FUNC" >> ImportError: /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol "ERR_GET_FUNC" >> ImportError: /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol "ERR_GET_FUNC" >> >> It is possible that this is related to some oddities of my >> context for this. But I figured I'd ask the general question >> anyway. > > I haven't seen this. My v7 environments (chroot and /usr/lib32) have > only libssl.so.3, not .111, so they must be using OpenSSL 3.0. But is the phython3 use by kyua of aarch64 code? armv7 code? # file /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua: ELF 32-bit LSB executable, ARM, EABI5 version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, FreeBSD-style, for FreeBSD 14.0 (1400092), not stripped So: armv7 for my lib32 testing activity. > Which version of kyua is this running (32 or 64 bit)? armv7 (so: 32-bit). This is using my way of causing more code to be armv7 instead of aarch64 processes for lib32 testing than I expect your testing technique ends up with. # file /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua: ELF 32-bit LSB executable, ARM, EABI5 version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, FreeBSD-style, for FreeBSD 14.0 (1400092), not stripped For reference: /usr/obj/DESTDIRs/main-CA7-chroot/usr/lib/libssl.so /usr/obj/DESTDIRs/main-CA7-chroot/usr/lib/libssl.so.30 As for the aarch4 boot environment: /usr/lib/libssl.so /usr/lib/libssl.so.30 There are no *.111* files on the system other than some old log files or other archiving of old things in 2 separate old-stuff directory trees that are not in use. === Mark Millard marklmi at yahoo.com