RE: No iconv() implementation found in C library or libiconv

[Xu Qiang <Qiang Xu fujixerox com>]

Marcus wrote:
> Because the allowed values of the --with-libiconv flag limit it.
> Output from `./configure --help`:
> [...]
>   --with-libiconv=[no/gnu/native]
>                           use the libiconv library
> [...]
> 
> After reading this and the environment variables and configure flags
> passed by the port, one can make up his own build process (thus I
> recommended you to read it):

Just find out this point. Thank you. Previously when I was compiling fontconfig 2.3.1, it can't find expat library although expat 1.95.8 had already been installed. So I use this method (--with-expat=/usr/local) to solve it. 

It is my fault that I didn't notice the values of the argument "--with-libiconv" are limited. I took it for granted the value must be the path of the needed module. 
 
> CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib -lintl" \
> ./configure --with-libiconv=gnu
> 
> "Why I need to pass CPPFLAGS and LDFLAGS?", you may ask. Because the
> configure script needs to know, where it can look for the matching
> libraries and headers for iconv et al.. intl is needed for i18n
> support. 

Thanks for your clear explanation. I run it as: 
-------------------------------------------------------
./configure --with-libiconv=gnu CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib
-------------------------------------------------------
and continue to "make" successfully. Ohoh, just forgot to add "-lintl" option, will re-compile it. Btw, you said it is for i18n support, what is i18n? Sorry for my dumb.

>> Btw, the various patches in that URL are all irrelavent to libiconv problem 
> Yes, but keep in mind, that they are not irrelevant, if you want to
> use the glib with threads in any way.

Can I apply these patches manually, instead of through the ports system?

You are so helpful, thanks, 

Regards,
Xu Qiang