From owner-freebsd-ports@FreeBSD.ORG  Sun Feb 23 12:43:58 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id DF33E9F9
 for <freebsd-ports@freebsd.org>; Sun, 23 Feb 2014 12:43:58 +0000 (UTC)
Received: from mailrelay002.isp.belgacom.be (mailrelay002.isp.belgacom.be
 [195.238.6.175]) by mx1.freebsd.org (Postfix) with ESMTP id 739281921
 for <freebsd-ports@freebsd.org>; Sun, 23 Feb 2014 12:43:57 +0000 (UTC)
X-Belgacom-Dynamic: yes
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmgGAPXrCVNbsIvO/2dsb2JhbABZgwa+aIMHgQUXdIIlAQEEATocIwULCxgJJQ8qHgaIEAwBx2sXjmQHhDgBA5gzkiiDLjs
Received: from 206.139-176-91.adsl-dyn.isp.belgacom.be (HELO
 kalimero.tijl.coosemans.org) ([91.176.139.206])
 by relay.skynet.be with ESMTP; 23 Feb 2014 13:43:51 +0100
Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org
 [127.0.0.1])
 by kalimero.tijl.coosemans.org (8.14.8/8.14.8) with ESMTP id s1NChnZT001777;
 Sun, 23 Feb 2014 13:43:50 +0100 (CET)
 (envelope-from tijl@FreeBSD.org)
Date: Sun, 23 Feb 2014 13:43:49 +0100
From: Tijl Coosemans <tijl@FreeBSD.org>
To: "Thomas Mueller" <mueller6724@bellsouth.net>
Subject: Re: libiconv pulled in by pkg upgrade? lots of errors after that
Message-ID: <20140223134349.54f75899@kalimero.tijl.coosemans.org>
In-Reply-To: <847746.72638.bm@smtp120.sbc.mail.gq1.yahoo.com>
References: <201402230851.s1N8pX2J066307@mech-cluster241.men.bris.ac.uk>
 <847746.72638.bm@smtp120.sbc.mail.gq1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-ports@freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Feb 2014 12:43:58 -0000

On Sun, 23 Feb 2014 10:57:12 +0000 (UTC) Thomas Mueller wrote:
> From other posts on emailing lists, I see libiconv from ports supports
> utf-8, while base (>=10) does not.

No, utf-8 works fine with base iconv.  Base iconv does not recognise the
special encoding named "wchar_t" which means whatever encoding is used for
the C/C++ type wchar_t with libiconv.

> Now I want to know what would happen if I rebuild system with 
> WITHOUT_ICONV=yes
> in /etc/src.conf
> and use libiconv from ports.
> 
> Would it work, and would I have to rebuild all ports?

It would work and it's probably easiest to rebuild all ports.  Technically
you only need to rebuild these packages:

grep -Rl __bsd_iconv /usr/local | xargs -n1 pkg which | sed 's/.* //' | sort -u

> It seems including libiconv in base has adverse side effects, the two
> can clash when both base and ports libiconv are installed.

The two can coexist.  It's just that some care must be taken during
compilation.