xlimits.h for embedded targets

[Joel Sherrill]

> This may be the problem. What in linits.h does gcc care about, other
> then those values it provides?

Nothing that I know of.

> This hack probably exists to allow gcc to be installed in places where the
> O/S limits.h header file is off limits, i.e. supplied by another compiler.
> We should be doing it THE OTHER WAY AROUND for cross targets: it is the
> O/S limits.h that should include_next the gcc limits.h. n'est pas? You as
> the RTEMS author have control over this. Make your limits.h include_next
> the compiler's limits.h, and make sure that gcc does *not* find it:-)
> 
> joel@OARcorp.com said:
> > Then maybe newlib should be "fixing" gcc's limits.h rather than the 
> > other way around.   
> 
> Yes! I think so. Makes sense to me, no?

I think this is a workable solution.  I will have to look at the
installation procedure as well as the search order to make sure this will
work but fundamentally this is the only way this can be made to work if
you install your limits.h after gcc has done its own.

--joel