From owner-freebsd-current@FreeBSD.ORG  Wed Oct 22 22:42:05 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 765CF16A4B3; Wed, 22 Oct 2003 22:42:05 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8A80B43F85; Wed, 22 Oct 2003 22:42:04 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h9N5fsBR011089;
	Thu, 23 Oct 2003 01:41:54 -0400 (EDT)
Date: Thu, 23 Oct 2003 01:41:54 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Peter Wemm <peter@wemm.org>
In-Reply-To: <20031023041544.068CD2A7EA@canning.wemm.org>
Message-ID: <Pine.GSO.4.10.10310230127410.6338-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: re@freebsd.org
cc: current@freebsd.org
cc: "M. Warner Losh" <imp@bsdimp.com>
cc: kris@obsecurity.org
Subject: Re: __fpclassifyd problem 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: deischen@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Oct 2003 05:42:05 -0000

On Wed, 22 Oct 2003, Peter Wemm wrote:

> Daniel Eischen wrote:
> > If it's just __fpclassifyd(), can you just add a compatability
> > hack to libm so it works with both libc 4.0 and 5.x?  You
> > can make __fpclassifyd a weak definition to the hack in libm.
> > I suppose you could also add __fpclassfyd() to libc 4.0.
> 
> We tried this at usenix, but it still didn't work.  Obviously there is more
> going on.

I guess so.  That's weird because it seems like it should work.

-- 
Dan Eischen