Again problem with atof / sscanf / strtof and float's range

[David McCullough]

Jivin Mathias.Krause at de.telex.com lays it down ...
> > > it's an old uClibc to be sure
> > 
> > Clarifying: uCLinux has been known to use old versions of uClibc 
> andBusyBox. 
> > Just because they built it in August of this year doesn't mean they were 
> 
> > using an up-to-date version of the package when they did so.  (They 
> often 
> > heavily modify their packages, so resyncing with the upstream version 
> can be 
> > a bit of a pain for them.  The downside is you wind up with this kind of 
> 
> > problem, which is quite possibly fixed in the current tree of uClibc, 
> but not 
> > the one uCLinux is using.)
> 
> Thank you all for your help. So, ok. Let's say that my problem is an old 
> bug
> in -old- uClibc. So, what can i do to solve the problem? 

Most of the time,  if you know where the problem is you can just take
the C/header files from the latest version and pop them it.  If not you
can at least check the changes through the uClibc web interface to see
if anyone has fixed something and apply the patches manually.

The dist versions are always based off the tarball uClibc release of the
same version.  There are a few changes,  some of which have just pulled
in newer versions as mentioned above,  others are to make it work in the
dist,  some are to get platforms working as expected.

Cheers,
Davidm

-- 
David McCullough,  david_mccullough at securecomputing.com,   Ph:+61 734352815
Secure Computing - SnapGear  http://www.uCdot.org http://www.cyberguard.com