On Thu, Apr 23, 2015 at 5:56 PM, Clemens Lang <cal@macports.org> wrote:
So if you get these link errors, the problem almost always is that you
adjusted your library search path, but not the corresponding header
search path and you're actually compiling against Apple's iconv.h but
MacPorts libiconv.dylib (or vice-versa).

Those are coming from a library already built against Apple's libiconv, but being linked against MacPorts' libiconv.

--
brandon s allbery kf8nh                               sine nomine associates
allbery.b@gmail.com                                  ballbery@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net