configure problem

[Roland McGrath]

> When I try to build libc in a minimal chroot environment, configure 
> fails while testing cpp functionality, because it uses <assert.h> for 
> the tests, and assumes it's present (which it isn't)

Yes, this is arguably a bug in Autoconf.  It would be better to use
limits.h or stddef.h.  But I think there are other problems with empty
include/lib trees (the same thing bites when freshly setting up a
cross-compilation environment).