From owner-cvs-src@FreeBSD.ORG Fri Jul 30 00:51:55 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAE6616A4CE; Fri, 30 Jul 2004 00:51:55 +0000 (GMT) Received: from VARK.homeunix.com (adsl-69-107-111-131.dsl.pltn13.pacbell.net [69.107.111.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8530F43D46; Fri, 30 Jul 2004 00:51:55 +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 i6U0qIXC001325; Thu, 29 Jul 2004 17:52:18 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i6U0qIW3001324; Thu, 29 Jul 2004 17:52:18 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Thu, 29 Jul 2004 17:52:18 -0700 From: David Schultz To: Scott Long Message-ID: <20040730005218.GA1247@VARK.homeunix.com> Mail-Followup-To: Scott Long , src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG References: <200407091001.i69A1A6V051028@repoman.freebsd.org> <41097469.10807@samsco.org> <20040729222415.GA728@VARK.homeunix.com> <4109853F.3090508@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4109853F.3090508@samsco.org> cc: cvs-src@FreeBSD.ORG cc: src-committers@FreeBSD.ORG cc: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/msun/src e_scalb.c e_scalbf.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 00:51:56 -0000 On Thu, Jul 29, 2004, Scott Long wrote: > Is this going to hose people doing source upgrades from 5.2.1 to 5.3 > and/or 4.x to 5.3. I know that the latter is going to be tough for a > lot of other reasons, but loosing the former would be bad. Also, does > it affect binary compat of 4.x/5.2 programs on 5.3? Yep, I know, and I intend to fix the problem by having an implementation of isnan*() in libc and libm. (It needs to be in each, for different reasons.) The commit you responded to is actually related to fixing some slightly different source/binary compat problems; it was another commit that caused the breakage. The trouble is that there's a lot of cruft we need to support because we never bump libm's version number. We have to be able to link *any* of libc.so.{2,3,4,5} with libm.so.2, we need to support programs compiled with the 4.x math.h running with the 5.X libm.so.2, etc. As I said before, I'll try to look into it tonight. But at the moment, I have a lot going on in my day job...