Date: Wed, 13 Jun 2012 20:27:37 -0700 From: Tim Kientzle <tim@kientzle.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Possible fix for Perl failing with ../lib/auto/POSIX/POSIX.so: Undefined symbol "__flt_rounds" on ARM Message-ID: <D51F780F-37BA-4F38-BEE4-869229D60014@kientzle.com> In-Reply-To: <20120612202640.GO2337@deviant.kiev.zoral.com.ua> References: <4FCE211D.10204@semihalf.com> <0FE5C5BF-FADE-49BA-BF38-00018A752F14@kientzle.com> <4FD6FB72.10900@semihalf.com> <20120612084917.GL2337@deviant.kiev.zoral.com.ua> <4FD7669C.8030802@semihalf.com> <20120612202640.GO2337@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 12, 2012, at 1:26 PM, Konstantin Belousov wrote: > On Tue, Jun 12, 2012 at 05:56:12PM +0200, Jan Sieka wrote: >> Both versions work indeed. I have analysed other architectures'=20 >> lib/libc/<arch>/Symbol.map files and __flt_rounds should go into = FBSD_ and=20 >> *not* into FBSDprivate section. I have verified that at least one of = the=20 >> Perl's libraries (POSIX.so) links to __flt_rounds. Python also links = to=20 >> this function. So to the best of my knowledge current patch is the=20 >> righteous one. >=20 > Let me restate my point again. It does not matter whether some = application > uses the symbol. It does matter whether the symbol is considered the = part > of exported stable ABI, intended for use by applications. If it is, = then > FBSD_1.X is the right namespace, otherwise symbol should be moved to > private and existing usage fixed. That particular symbol is in FBSD_1.0 for amd64, i386, ia64, powerpc, = powerpc64, sparc64. It's in FBSDPrivate_1.0 for arm. It's not defined for mips at all. The latter two seem to be bugs; I just committed r237039 to fix arm. I haven't checked the situation on mips. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D51F780F-37BA-4F38-BEE4-869229D60014>