Date: Thu, 23 Nov 2023 04:24:16 -0800 From: Mark Millard <marklmi@yahoo.com> To: John F Carr <jfc@mit.edu> Cc: FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: Undefined __aeabi_uidivmod in 14.0 armv7 Message-ID: <0A4098ED-2084-4F9B-8006-7832E8333CAC@yahoo.com> In-Reply-To: <0EBEB2B6-198D-47C5-8715-02F19EF5ED06@mit.edu> References: <0EBEB2B6-198D-47C5-8715-02F19EF5ED06@mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 23, 2023, at 04:15, John F Carr <jfc@mit.edu> wrote: > Before submitting this as a bug, I want to know which component is at = fault. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271087 > I upgraded my armv8 host and armv7 jail to 14.0. Using poudriere to = build > armv7 packages, ruby33 fails: >=20 > making encs > Generating RDoc documentation > ld-elf.so.1: /usr/local/lib/libunwind.so.8: Undefined symbol = "__aeabi_uidivmod" > *** Error code 1 >=20 > I confirmed that libunwind.so does have a dynamic dependency > on __aeabi_uidivmod. That function is defined in /usr/lib/libgcc.a > as a wrapper around __udivmodsi4 in the same library. It is > not defined in /lib/libgcc_s.so. >=20 > Linking something against libgcc.a would fix this. >=20 > The _aeabi_ family of functions, as far as I can tell, is only used > with -target arm-none-eabi and not with the default target. Using > better compiler flags would also fix this. >=20 > So... >=20 > Is this a bug in base: libgcc.so lacks or does not export = __aeabi_uidivmod? > Is this a bug in base: the compiler does not link libgcc.a? > Is this a bug in devel/libtool: libtool does not link libgcc.a? > Is this a bug in devel/libunwind? > Is this a bug in lang/ruby33? > Is this a bug in some unknown component compiled for EABI instead of = FreeBSD? =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?0A4098ED-2084-4F9B-8006-7832E8333CAC>