Re: build failure when system does not provide MB_CUR_MAX

[Simon Josefsson]

Mike Frysinger <address@hidden> writes:

> On Tuesday 26 May 2009 19:13:51 Bruno Haible wrote:
>> Mike Frysinger wrote:
>> > it's disabled explicitly because we dont want multibyte sucking up space
>> > on a system that doesnt need it.  there are a few packages (like zile)
>> > which dont currently have a way of disabling the multibyte workarounds.
>>
>> Do you think it will take less space if each of these packages had a copy
>> of some gnulib-provided multibyte + locale code linked in _statically_,
>> than when uClibc has it linked in _once_, in a shared library? I don't
>> think so.
>
> i never said that.  the point was to fix these packages that require 
> multibyte 
> so that they dont have any multibyte cruft either.

I think that is a much better solution than making gnulib re-implement
more of ANSI C multibyte stuff.  And if you do that work, the
application won't need MB_CUR_MAX, will it?  So the problem is gone.

/Simon