Date: Wed, 29 Jan 2014 09:06:43 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Dmitry Marakasov <amdmi3@amdmi3.ru> 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: <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org> In-Reply-To: <20140129022743.GO52820@hades.panopticon> References: <20140129022743.GO52820@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_250C6024-8780-4FA8-86C5-9739F34A2DC9 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 29 Jan 2014, at 03:27, Dmitry Marakasov <amdmi3@amdmi3.ru> 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. -Dimitry --Apple-Mail=_250C6024-8780-4FA8-86C5-9739F34A2DC9 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlLotpoACgkQsF6jCi4glqMqgACg81p6X0OnBVMEdJ0UrggYrqjD SnIAnR7ermQWFnqM5kFoY17BnhzZr1kU =/e3h -----END PGP SIGNATURE----- --Apple-Mail=_250C6024-8780-4FA8-86C5-9739F34A2DC9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239>