libiconv

Ryan Schmidt ryandesign at macports.org
Sat Jan 5 15:26:31 PST 2008


On Jan 5, 2008, at 17:23, Takeshi Enomoto wrote:

> I have received an error report on g95.
> <http://trac.macosforge.org/projects/macports/ticket/13841>
>
> It is related to MacPorts' libiconv.
> MacPorts' libiconv does not have symbols iconv_*.
> There are libiconv_* instead.
>
> System's libiconv have both.
>
> A quick google search tells me that it is a cause of
> build failure of a few other packages.

I do recall seeing this error reported before.

> Could you tell me if
> 1) iconv_* are deprecated and I should rewrite them to libiconv_*,
> 2) system's libiconv should be used, or
> 3) I should wait an update of libiconv package?

I don't know the answer to any of those questions. Well, except for  
question 2, where I think the answer is "no" because of the reasons  
stated in the MacPorts FAQ (reasons for why MacPorts uses its own  
libraries and not the system libraries). I can ask the developers of  
iconv why those functions are not present.




More information about the macports-dev mailing list