From owner-freebsd-current@FreeBSD.ORG Wed Jan 29 14:45:22 2014 Return-Path: Delivered-To: freebsd-current@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 A44B61E6; Wed, 29 Jan 2014 14:45:22 +0000 (UTC) Received: from smtpout3.timeweb.ru (smtpout3.timeweb.ru [92.53.117.25]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 583FD1119; Wed, 29 Jan 2014 14:45:22 +0000 (UTC) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1W8WOF-0002yn-1t; Wed, 29 Jan 2014 18:45:19 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id A53BCF8A; Wed, 29 Jan 2014 18:45:18 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 7CC5520A0C; Wed, 29 Jan 2014 18:45:18 +0400 (MSK) Date: Wed, 29 Jan 2014 18:45:18 +0400 From: Dmitry Marakasov To: Dimitry Andric Subject: Re: System libc++ isn't fully compatible with clang 3.4 from ports Message-ID: <20140129144518.GR52820@hades.panopticon> References: <20140129022743.GO52820@hades.panopticon> <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-current@FreeBSD.org, David Chisnall , Brooks Davis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 14:45:22 -0000 * Dimitry Andric (dim@FreeBSD.org) wrote: > > JFYI, I've just ran into shortcoming of libc++ from 10-RELEASE when used > > with clang 3.4 from ports: > ... > > The cause: http://llvm.org/bugs/show_bug.cgi?id=17798, was fixed in > > libc++ r194154. We probably need to update libc++ or at least backport > > this into stable branches if we want to support clang 3.4 in ports. > > Hm, which port is having problems with this? I have built quite a large > set, and never encountered this issue. > > In any case: yes, it is quite long overdue for a libc++ update. :-) I > will have a look tonight. New version of games/spring (not in ports yet). std::function and lambdas are not that widely used for this problem to be common, but some time we may run into it for some critical software. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru