Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Oct 2003 03:30:56 -0600 (MDT)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        sgk@troutmask.apl.washington.edu
Cc:        kris@obsecurity.org
Subject:   Re: __fpclassifyd problem
Message-ID:  <20031020.033056.24857330.imp@bsdimp.com>
In-Reply-To: <20031019221341.GA32851@troutmask.apl.washington.edu>
References:  <20031019204629.GC49466@rot13.obsecurity.org> <3F92FC99.8010802@freebsd.org> <20031019221341.GA32851@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20031019221341.GA32851@troutmask.apl.washington.edu>
            Steve Kargl <sgk@troutmask.apl.washington.edu> writes:
: 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. 

I tend to agree due to some weirdness that forced the libc bump.
However, this would then have to includ all ports libraries too.
Bumping all ports libraries and having a viable ports system that
built on both 4.x and 5.x would then become nightmarish because you'd
not want to bump them on 4.x.

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031020.033056.24857330.imp>