Re: Possible fix for Perl failing with ../lib/auto/POSIX/POSIX.s

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

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"