Date: Wed, 29 Jan 2014 18:45:18 +0400 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Dimitry Andric <dim@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, David Chisnall <theraven@FreeBSD.org>, Brooks Davis <brooks@FreeBSD.org> Subject: Re: System libc++ isn't fully compatible with clang 3.4 from ports Message-ID: <20140129144518.GR52820@hades.panopticon> In-Reply-To: <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org> References: <20140129022743.GO52820@hades.panopticon> <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140129144518.GR52820>