Re: What does "properly support iconv" in git Makefile (NO_ICONV) mean?

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

 



On Tue, Sep 05 2006 at 01:16, Fernando J. Pereda wrote:
> On Tue, Sep 05, 2006 at 01:08:57AM +0200, Jakub Narebski wrote:
>> To add autoconf support for checking if NO_ICONV has to be defined
>> (Define NO_ICONV if your libc does not properly support iconv.)
>> one needs to know what does "properly support iconv" mean.
>> 
>> The commit message of a commit which introduced this compilation 
>> variable (commit b6e56eca8a4eb74a86e9f2d99aa480c665458aa7) tells:
>> 
>>     Systems using some uClibc versions do not properly support
>>     iconv stuff.
>> 
>> At what exactly iconv fail? What should the test to put in
>> configure.ac check?
> 
> As far as I know, iconv stuff is not supported on uClibc. Thats the
> reason I sent the patch. Gentoo bug #115826 [1].
> 
> You should probably set it if you are building for uClibc. Not sure
> how you'd test that in configure.ac though.
> 
> [1] https://bugs.gentoo.org/show_bug.cgi?id=115826

Gaah, I have some problems accessing the Gentoo bug database.
Is the problem that iconv does not exist in libc, or it exist but 
misbehaves?
-- 
Jakub Narebski
Poland
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]