Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Jul 2023 11:00:29 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        Mike Karels <mike@karels.net>
Cc:        Current FreeBSD <freebsd-current@freebsd.org>
Subject:   Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"
Message-ID:  <D819DA9F-3C28-4ABE-B27C-A1C4E6A77963@yahoo.com>
In-Reply-To: <24B73E3F-204F-415F-9B5F-5AA4C653025C@yahoo.com>
References:  <1E426C5E-B363-4C76-A952-48EF404F6557.ref@yahoo.com> <1E426C5E-B363-4C76-A952-48EF404F6557@yahoo.com> <09E15258-505F-48A0-9F0A-35A2F2CDC8A9@karels.net> <24B73E3F-204F-415F-9B5F-5AA4C653025C@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 10, 2023, at 10:55, Mark Millard <marklmi@yahoo.com> wrote:

> On Jul 10, 2023, at 09:45, Mike Karels <mike@karels.net> wrote:
>=20
>> On 10 Jul 2023, at 10:56, Mark Millard wrote:
>>=20
>>> The subject line's question was prompted by
>>> . . ./hazmat/bindings/_openssl.abi3.so related notices
>>> in a kyua report:
>>>=20
>>> # kyua report --verbose =
--results-file=3Dusr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-06463=
2-752785 2>&1 | grep "Undefined symbol" | sort -u
>>> +ImportError: =
/usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cr=
yptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol =
"ERR_GET_FUNC"
>>> ImportError: =
/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_opens=
sl.abi3.so: Undefined symbol "ERR_GET_FUNC"
>>> ImportError: =
/usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cr=
yptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol =
"ERR_GET_FUNC"
>>>=20
>>> 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.
>>=20
>> 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.
>=20
> But is the phython3 use by kyua of aarch64 code? armv7 code?
>=20
> # 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
>=20
> So: armv7 for my lib32 testing activity.
>=20
>> Which version of kyua is this running (32 or 64 bit)?
>=20
> 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.
>=20
> # 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
>=20
> For reference:
>=20
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/lib/libssl.so
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/lib/libssl.so.30
>=20
> As for the aarch4 boot environment:
>=20
> /usr/lib/libssl.so
> /usr/lib/libssl.so.30

I forgot to list:

/usr/lib32/libssl.so.30
/usr/lib32/libssl.so

Sorry for the confusion.

> 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.


=3D=3D=3D
Mark Millard
marklmi at yahoo.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D819DA9F-3C28-4ABE-B27C-A1C4E6A77963>