> I posted about this over the weekend without any response.  libm
> really confuses ar or something.  I compile everything else (all the
> libs, etc.) without any problem, but libm acts *really* weird.  My cc
> and ar are both current from the sources the day before yesterday and
> are statically linked.  I can have it break on one file then pass if I
> restart the compile:

Do you mean "ar" is up to date or "as"?  "as" recently had to change to support
new features of the compiler; make sure "as" is up to date.





------------------------------------------------------------------------------