From owner-freebsd-ports@FreeBSD.ORG Sat May 16 19:02:11 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59B5B3C4 for ; Sat, 16 May 2015 19:02:11 +0000 (UTC) Received: from mail.bein.link (bein.link [37.252.124.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1F41317BE for ; Sat, 16 May 2015 19:02:10 +0000 (UTC) Received: from thinkpad.localnet (home.bein.link [188.134.8.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bein.link (Postfix) with ESMTPSA id 659CE1AF161; Sat, 16 May 2015 19:02:02 +0000 (UTC) From: Maxim V Filimonov To: freebsd-ports@freebsd.org Reply-To: che@bein.link Cc: Kevin Oberman Subject: Re: net/mediatomb fails to build Date: Sat, 16 May 2015 22:02:03 +0300 Message-ID: <2117431.UGtR5A8AW4@thinkpad> User-Agent: KMail/4.14.3 (FreeBSD/10.1-RELEASE-p10; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <5529321.PvBpsCEs9n@thinkpad> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 May 2015 19:02:11 -0000 On Saturday 16 May 2015 10:04:06 Kevin Oberman wrote: > The issue that caused the BROKEN designator only looks to show up if > clang-3.6 is used. Older versions of clang seem to work fine. The iconv > issue is unrelated and the patch in hte ticket should fix that, so, if you > are not runing current and are using the base compiler, just apply the > iconv fix from the ticket (200232), comment out the BROKEN and build. The > USER/GROUP issue also needs to be fixed, but does not prevent building, > installing or using it. Thank you. As I wrote in the PR itself, it built just fine on my machine after applying the provided patch. They have also committed that by now, so everything is fine for now. -- wbr, Maxim Filimonov