[Top][All Lists]

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

localcharset should not use directly GLIBC21 check

From: Timo Teras
Subject: localcharset should not use directly GLIBC21 check
Date: Thu, 25 Jul 2013 20:39:48 +0300

Currently localcharset uses m4/glibc21.m4 (ac_cv_gnu_library_2_1) to
figure out if charset.alias needs to be installed or not.

However, a separate ac_cv_iconv_has_standard_charset_names or similar
would be better so it can be controlled better. Especially important
with musl c library, where charset.alias is not needed, but where we do
not want to appear as GNU C library or uClibc.

Additional confusion arises since:
m4/glibc2.m4 (ac_cv_gnu_library_2) checks for glibc 2+ AND NOT uclibc
m4/glibc21.m4 (ac_cv_gnu_library_2_1) checks for glibc 2.1+ OR uclibc

While glibc21.m4 is used only for localcharset in gnulib, the same
cache name value could be used for various other purposes in other

So please add separate separate config item for localcharset, even if
it defaults to ac_cv_gnu_library_2_1.


reply via email to

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