Building GNU tar from scratch failed because lib/getopt_int.h's declaration
of _getopt_internal specified a different signature from /usr/include/getopt.h
on my host (Debian GNU/Linux 3.1). I tracked it down to the fact that GNU
tar uses both argp and getopt, and argp was asking for the substitute
Bruno Haible <[EMAIL PROTECTED]> writes:
> - mbchar: Multibyte character data type.
> - mbiter: Iterating through multibyte strings.
> - mbfile: Multibyte character I/O.
This looks really useful. Thank you for writing this--it should
make dealing with multibyte characters much simpler.
Is
> * Paul Eggert <[EMAIL PROTECTED]> [2005-08-15 17:06:58 -0700]:
>
> Bruno Haible <[EMAIL PROTECTED]> writes:
>
>> This patch should work. No version of g++ in the 3.2.*, 3.3.*, 3.4.*,
>> 4.0.[01] series supports the [__restrict] syntax.
>
> Thanks. I installed that patch,
Thanks.
Would you plea
> > Thus, wouldn't it be wise to fix strcasecmp itself, and include it
> > unconditionally in GnuLib ?
>
> Yes. Here's a patch to that effect. (Completely untested so far. Also
> quite inefficient. One can do better with mbrtowc().)
Well, that code was broken. And a similar code I wrote based on m
Hi,
Prompted by the need to implement a correct strcasecmp() function, I
added to gnulib the modules:
- mbchar: Multibyte character data type.
- mbiter: Iterating through multibyte strings.
- mbfile: Multibyte character I/O.
These modules were written in 2001, mbchar and mbiter by me, mbfi
Paul Eggert wrote:
> This sort of macro will cause warnings with GCC and other compilers
> if you use it in a context like this:
>
>if (foo)
> gl_tls_key_init (name, destructor);
>
> because the compiler will warn about possible if-then-else nesting
> problems. The usual do { ... } while
