From owner-freebsd-current@FreeBSD.ORG Sun Oct 19 15:13:42 2003 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 D04B316A4B3; Sun, 19 Oct 2003 15:13:42 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AACB43F3F; Sun, 19 Oct 2003 15:13:42 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) h9JMDfOH032944; Sun, 19 Oct 2003 15:13:41 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)h9JMDfoR032943; Sun, 19 Oct 2003 15:13:41 -0700 (PDT) (envelope-from sgk) Date: Sun, 19 Oct 2003 15:13:41 -0700 From: Steve Kargl To: Scott Long Message-ID: <20031019221341.GA32851@troutmask.apl.washington.edu> References: <3F92E129.10307@veidit.net> <20031019204629.GC49466@rot13.obsecurity.org> <3F92FC99.8010802@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F92FC99.8010802@freebsd.org> User-Agent: Mutt/1.4.1i cc: re@freebsd.org cc: current@freebsd.org cc: Kris Kennaway Subject: Re: __fpclassifyd problem 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: Sun, 19 Oct 2003 22:13:42 -0000 On Sun, Oct 19, 2003 at 03:05:29PM -0600, Scott Long wrote: > Kris Kennaway wrote: > > > >This symbol is defined in libc.so.5. One way you can see this problem > >is if you are running a 4.x binary that links to libm.so.2 on a 5.x > >system, because libm has the same version number in 5.x but is not > >binary compatible. So the 4.x binary links to libc.so.4 and > >libm.so.2, and the latter is actually a 5.x library that expects to > >have __fpclassifyd resolved by linking with libc.so.5. Is it the case > >on your system that you have old 4.x binaries installed? > > > >Kris > > We need to resolve this before 5.2 in some fashion. It looks like the > easiest thing to do is bump libm. Is this advisable? > I sent in an email *along time ago* about this type of problem. See the fallout due to revision 1.24 of lib/libc/stdio/findfp.c. IMHO, all shared libraries versions should have been bumped in going from 4.x to 5.0. -- Steve