From owner-freebsd-current@FreeBSD.ORG Mon Jul 5 02:26:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38A6716A4CE for ; Mon, 5 Jul 2004 02:26:16 +0000 (GMT) Received: from VARK.homeunix.com (adsl-69-107-108-110.dsl.pltn13.pacbell.net [69.107.108.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id F413E43D55 for ; Mon, 5 Jul 2004 02:26:15 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.11/8.12.10) with ESMTP id i652PsJF008506; Sun, 4 Jul 2004 19:25:54 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i652PsrF008505; Sun, 4 Jul 2004 19:25:54 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Sun, 4 Jul 2004 19:25:54 -0700 From: David Schultz To: Kris Kennaway Message-ID: <20040705022554.GA8215@VARK.homeunix.com> Mail-Followup-To: Kris Kennaway , current@FreeBSD.ORG References: <40DDEADA.7000102@obsecurity.org> <20040701020854.GA16944@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040701020854.GA16944@xor.obsecurity.org> cc: current@FreeBSD.ORG Subject: Re: libm binary compat still broken (diablo-jdk does not run) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2004 02:26:16 -0000 On Wed, Jun 30, 2004, Kris Kennaway wrote: > Looks like libm binary compatibility with 4.x was never quite fixed :-( > [...] > > ===> Building for jzip.org-0.2.0 > > /usr/libexec/ld-elf.so.1: /lib/libm.so.2: Undefined symbol "__fpclassifyd" Sigh. Steve is right. The library's major version number should have been bumped long ago. However, if this is the *only* thing that's broken w.r.t. backwards binary compatibility, I think I can fix it another way. I'll see if I can make the isnan() macro point to the isnan() function when given a double input, and the isnanf() function when given a float input.