From owner-svn-ports-head@FreeBSD.ORG Sun Jun 15 14:02:37 2014 Return-Path: Delivered-To: svn-ports-head@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 2F5BE1E1 for ; Sun, 15 Jun 2014 14:02:37 +0000 (UTC) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [78.111.72.186]) by mx1.freebsd.org (Postfix) with ESMTP id 7533D2D79 for ; Sun, 15 Jun 2014 14:02:36 +0000 (UTC) Received: (qmail 41488 invoked by uid 80); 15 Jun 2014 14:02:29 -0000 Received: from dsdf-4d0a7f17.pool.mediaWays.net (dsdf-4d0a7f17.pool.mediaWays.net [77.10.127.23]) by avocado.salatschuessel.net (Horde Framework) with HTTP; Sun, 15 Jun 2014 16:02:29 +0200 Date: Sun, 15 Jun 2014 16:02:29 +0200 Message-ID: <20140615160229.Horde.OcUGIOns2S76M7snB1ZoAA1@avocado.salatschuessel.net> From: Oliver Lehmann To: marino@freebsd.org Subject: Re: svn commit: r357767 - head/net/cyphesis References: <201406141111.s5EBBCgV016094@svn.freebsd.org> <539C8682.3030603@marino.st> <20140614175243.GD67971@mouf.net> <539C8E46.1010803@marino.st> <20140614185459.GA68684@mouf.net> <539C9E30.2070505@marino.st> In-Reply-To: <539C9E30.2070505@marino.st> User-Agent: Internet Messaging Program (IMP) H5 (6.1.7) Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Cc: svn-ports-head@freebsd.org, Steve Wills , svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2014 14:02:37 -0000 John Marino wrote: >> Also, would adding USE_GCC help here? > > From what I could see of the build log, it should be relatively easy for > a knowledgeable person to fix it to work on any compiler. A real > attempt to fix it should be made before resorting to USE_GCC. But yes, > USE_GCC would be preferable to BROKEN IMO. The first error which triggers the build to abort is of course easy to fix by just adding #include and thats it. The errors which will occur after the first one are not easy to fix. I even mailed around with the author and it seems to be a bit complicated to fix them. I didn't heard back from him for a while so I'm going to mark it as broken as I don't have the time/energy to investigate any further. - USE_GCC does not help. - gcc-c++11-lib makes it compile a bit further but it fails later.