Re: __fpclassifyd problem

In message: <20031019221341.GA32851_at_troutmask.apl.washington.edu>
            Steve Kargl <sgk_at_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