[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lynx-dev] some glitch in "UCdomap.c" wrt "libiconv"
From: |
Henry Nelson |
Subject: |
Re: [Lynx-dev] some glitch in "UCdomap.c" wrt "libiconv" |
Date: |
Fri, 23 Jun 2006 17:21:55 +0900 |
User-agent: |
Mutt/1.5.11 |
On Sat, Jun 17, 2006 at 01:11:23PM +0900, Henry Nelson wrote:
> The only warnings I get now (after patch in previous mail) are the following:
>
> gcc -I/usr/local/include -DHAVE_CONFIG_H -DNO_CHARSET_shift_jis=0 [...]
> euc_jp=0 -DNO_CHARSET_utf_8=0 -DNO_CHARSET_us_ascii=0 -DNO_CHARSET_[...]
> -DNO_CHARSET_iso_8859_1=0 -DLOCALEDIR=\"/usr/local/share/locale\"[...]
> -Ichrtrans -I./chrtrans -I.. -I../src -I../WWW/Library/Implemen[...]
> -c ./UCdomap.c
> UCdomap.c: In function `UCTransUniCharStr':
> UCdomap.c:955: warning: passing arg 2 of `libiconv' from incompatible pointer
It might be possible to use the AM_ICONV macro to get rid of this warning:
The `AM_ICONV' macro tests for the presence of the POSIX/XSI `iconv'
function family in either the C library or a separate `libiconv'
library. If found, it sets the `am_cv_func_iconv' variable to `yes';
it defines `HAVE_ICONV' to 1 in the autoconf generated configuration
=> file (usually called `config.h'); it defines `ICONV_CONST' to `const'
=> or to empty, depending on whether the second argument of `iconv()' is
=> of type `const char **' or `char **'; ...
__Henry
"Using Lynx is like wearing a really good pair of shades: cuts out
the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
-- me, March 1999