>	drawback is that you will have all locale handling code linked into
>	your static library, once you use printf().  printf pulls in mbrtowc,
>	and it will pull in EUC/UTF2/UTF8/whatever handling code as a result.
>	if we want a option to compile a binary with no locale support,
>	we may want to ship libnolocale.a or whatever to override locale code.
>	(i don't know what is the common practice for this.  i remember
>	freebsd shipped multibyte locale in libxpg4, however it looked bogus
>	and was not a standard practice)

	the above issue is removed (printf no longer pull in multibyte locale
	stuff, a call to setlocale does), so static binaries (without need for
	multibyte locale stuff) will not have to link extra *.o.

itojun