[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: |
Bruno Haible |
Subject: |
Re: build failure when system does not provide MB_CUR_MAX |
Date: |
Wed, 27 May 2009 01:13:51 +0200 |
User-agent: |
KMail/1.9.9 |
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.
> you're saying this breakage is "by design" with gnulib, so that's that.
Yes, the design of gnulib is that the user should have a way to compile each
application on every kind of system. We support one way of doing so, not
necessarily your preferred way.
- gnulib does not support you if you use HP-UX cc without option "-Ae".
- gnulib does not support you if you have no C compiler or no linker
installed.
- gnulib does not support you if you make deliberate choices that go to
the opposite direction.
The usual disclaimer: If someone was to contribute good code that does what you
want, it could go into gnulib, despite all that I am saying. But I won't write
that code, given that you have such an easy way out.
Bruno