[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: build failure when system does not provide MB_CUR_MAX

From: Simon Josefsson
Subject: Re: build failure when system does not provide MB_CUR_MAX
Date: Wed, 27 May 2009 07:18:26 +0200
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]