Eric Blake <[EMAIL PROTECTED]> writes: > Here's my first cut at it. It currently assumes that absolute <wchar.h> > exists. I'm not sure whether it is worth trying to check for > HAVE_WCHAR_H, or to leave that until we actually get a report of a system > that needs it.
Yes, I'd leave it alone until then, given that we've had no other reports of problems. That being said, <http://www.busybox.net/lists/buildroot/2006-December/000708.html> suggests that uClibc lacks wchar.h, at least in some configurations. <http://sourceware.org/ml/crossgcc/2000-11/msg00116.html> suggests that <wchar.h> is missing in a standalone ARM processor environment. <http://www.arcknowledge.com/gmane.comp.gnu.findutils.bugs/2005-12/msg00048.html> says <wchar.h> is missing in OpenBSD 3.2 by default. So I suspect we'll run into the problem eventually. (But we can ask for help from whoever does run into it later....)
