libiconv pulled in by pkg upgrade? lots of errors after that

Scot Hetzel swhetzel at
Sun Feb 23 09:43:28 UTC 2014

On Sun, Feb 23, 2014 at 2:51 AM, Anton Shterenlikht <mexas at> wrote:
> pkg upgrade pulled libiconv.
> Now I get errors like:
>  # gphoto2 -l
> /usr/local/lib/libgphoto2/ Undefined symbol "__bsd_iconv_open"
>  firefox
> /usr/local/lib/firefox/ Undefined symbol "__bsd_iconv_open"
> If I delete libiconv, then I get:
>  firefox
> XPCOMGlueLoad error for file /usr/local/lib/firefox/
> Shared object "" not found, required by ""
> Couldn't load XPCOM.
> so I probably now need to rebuild all these ports
> manually:
> [1/1] Deleting libiconv-1.14_1...
> libiconv-1.14_1 is required by: glib-2.36.3_2 gobject-introspection-1.36.0_2 libIDL-0.8.14_1 polkit-0.105_1 cairo-1.10.2_7,2 pango-1.34.1_1 consolekit-0.4.3 librsvg2-2.36.4 gconf2-2.32.0_3, deleting anyway
> Anyway, I thought libiconv was gone for good
> from ports, as it is available in base from 10.
> I'm on 11-current, so not sure what's going on.
There are some ports (i.e php-iconvm devel/glib2) that require the
libiconv port due to they rely on a gnu feature that is not
implemented in FreeBSD'x posix compliant libiconv in base.

The message in devel/glib2/Makefile:

# iconv:wchar_t - our iconv in base doesn't support utf-8 -> wchar_t (boooo)
# (wchar_t is used by glibmm, rawtherapee triggered this)
USES= gettext gmake iconv:wchar_t pathfix pkgconfig shebangfix perl5


No electrons were maimed while sending this message. Only slightly bruised.

More information about the freebsd-ports mailing list