> strcasecmp: Support cross-compilation.
A similar error is:
checking whether newlocale with a null base works... configure: error: in
'/GNULIB/testdir-all':
configure: error: cannot run test program while cross compiling
Fixed like this:
2025-04-11 Bruno Haible
Hi,
Rudi Heitbaum wrote:
> checking for strcasecmp... yes
> checking whether strcasecmp works... configure: error: in
> '/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-13.0-devel/build/diffutils-3.12/.x86_64-libreelec-linux-gnu':
> configure: error: c
strcasecmp... yes
checking whether strcasecmp works... configure: error: in
'/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-13.0-devel/build/diffutils-3.12/.x86_64-libreelec-linux-gnu':
configure: error: cannot run test program while cross compiling
Regards
Rudi
The CI reports a compilation error on MSVC:
D:\a\ci-testdir-check\ci-testdir-check\testdir-all\gltests\test-strcasecmp.c(22):
error C2065: 'strcasecmp': undeclared identifier
This patch fixes it.
2025-02-17 Bruno Haible
strcasecmp, strncasecmp: Fix compilation err
I don't believe it. I just don't believe it.
Solaris, with its fame of being seminal regarding internationalization,
ships a buggy strcasecmp() function. The bug is reproducible in Solaris 10,
Solaris 11.4, Solaris 11 OpenIndiana, Solaris 11 OmniOS.
=
The functions strcasecmp, strncasecmp are provided by a single module:
'strcase'.
Similarly, the functions c_strcasecmp, c_strncasecmp are provided by a
single module: 'c-strcase'.
While this saves a little bit of module description and *.m4 code, it
has two drawbacks:
Hi Paul,
> Shouldn't regex be avoiding strcasecmp entirely?
> That is, couldn't there be a weird locale that considers
> the lower-case equivalent of "U" to be "uu", or something
> weird like that?
In such a locale, strcasecmp would not consider "U
On 04/24/2011 06:13 AM, Bruno Haible wrote:
> strcasecmp and strncasecmp are only missing on "old" platforms, according to
> the platforms x functions matrix. Here's a proposed patch:
>
>
> 2011-04-24 Bruno Haible
>
> strcase: Make module obsolet
strcasecmp and strncasecmp are only missing on "old" platforms, according to
the platforms x functions matrix. Here's a proposed patch:
2011-04-24 Bruno Haible
strcase: Make module obsolete.
* modules/strcase (Status, Notice): New fields.
*** modules/strcase.
Eric Blake wrote:
> The documentation was out-of-date. ... I'm pushing this.
Thanks. One more clarification: All modern platforms have strcasecmp and
strncasecmp.
2010-01-07 Bruno Haible
* doc/posix-functions/strcasecmp.texi: Clarify the platforms.
* doc/posix-f
The only reason for the case-insensitive comparison here is support
for Windows-like file names, right? So the issue is not worth our
worrying about (except perhaps as a warning that we should avoid
case-insensitive comparison whenever we can :-).
Not really. It's an option name, and options a
Paul Eggert wrote:
> However, here I had some performance problems with mbscasemcp. Given
> two multibyte strings A and B, I want to know whether A is an initial
> prefix of B, ignoring case during comparison; also, if A is a prefix
> of B, I need to know where in B the prefix ends (because I want
Paul Eggert wrote:
> I installed this. It adds a dependency of regex on localcharset,
Thanks. This improves regex on
- Mingw, which doesn't have nl_langinfo(CODESET) and where the locale
is usually set through system settings, not through environment variables,
- Cygwin, where nl_langinfo
I installed the following to fix the 'exclude' module to avoid
strcasecmp, and to modernize it to support FNM_EXTMATCH.
However, here I had some performance problems with mbscasemcp. Given
two multibyte strings A and B, I want to know whether A is an initial
prefix of B, ignoring c
I installed this. It adds a dependency of regex on localcharset,
which I'd rather avoid, but the alternatives seemed worse to me.
2007-02-14 Paul Eggert <[EMAIL PROTECTED]>
Fix regex code so it doesn't rely on strcasecmp.
* lib/regex_internal.h: Include
Bruno Haible <[EMAIL PROTECTED]> writes:
> Paolo Bonzini wrote:
>> I'm not sure how Turkish people would do lowercase translation
>> of English words. In other words, I'm not sure if they'd write the
>> hypothetical language Iris as İRİS or ırıs.
>
> This is one question to ask. The other consi
This consideration points to using
(a) c_strcasecmp (a, b) or
(b) c_strcasecmp (a, b) || mbscasecmp (a, b).
If your Turkish friend says he would write "ırıs", then it points to (b).
If not, i.e. if such a word is not considered like a Turkish word, it points
to (a).
I haven't asked ye
) or
(b) c_strcasecmp (a, b) || mbscasecmp (a, b).
If your Turkish friend says he would write "ırıs", then it points to (b).
If not, i.e. if such a word is not considered like a Turkish word, it points
to (a).
Btw, mbscasecmp not strcasecmp - because strcasecmp cannot work in Tu
case translation
of English words. In other words, I'm not sure if they'd write the
hypothetical language Iris as İRİS or ırıs. By the way, note that the
one whose pronunciation is closest to /i/, is the dotted İ/i, not the
dotless I/ı.
I don't think it's exact to say,
19 matches
Mail list logo
