Re: [xml] Using libiconv

On Tue, 3 Jul 2001 xml thewrittenword com wrote:
Sorry but this kind modyfication it is plain/big step back.
Instead patching use natural autoconf abilities and run
configure by:

$ CFLAGS="-I<iconv_prefix>/include" LDFLAGS="-L<iconv_prefix>/lib" ./configure

It won't work because you're using GNU libiconv with the system
iconv.h. They are incompatible. The only way to properly check for
-liconv is to AC_TRY_LINK and include iconv.h. You cannot do this with
AC_CHECK_LIB. Brian Stafford was right about this.

Forgive me what is the sens using libiconv when you have iconv in glibc ?
If someone have system with iconv in libc and additionaly have header
files for libiconv this rather slightly not correct situacion and from    
ths poin of view we can say "it is your private busines but this isn't
correct" :)

Link with libc with build in iconv and with libiconv probably will make
symbol clashes and can produce unuseable binaries when you first build
some applications using libxml configured for using iconv from libc and
after this rebuild and install libxml linked with libiconv (?). Of course 
static linking also can produce correct binaries.

I'm thinking only about detection libiconv installed in non-standart
<iconv_prefix> prefix on system without iconv in libc and above only can
cure only this cases.
Thinking about other cases IMHO isn't proper (?). Correct me if I'm wrong.

iconv detection IMHO can be performed as:

1) try find iconv in libc,
2) if not found in libc try find libiconv,
3) if not found libiconv system can't support iconv.

--with{,out}-iconv can be used only for obligatory using or not iconv
without depending on libc abilities or is libiconv is installed.

*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
Tomasz Kłoczko, sys adm|*e-mail: kloczek rudy mif pg gda pl*

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