Date: Wed, 30 Nov 2016 18:38:47 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference Message-ID: <bug-214863-29464-l5UyvSpE6A@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214863-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-214863-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214863 Dimitry Andric <dim@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bapt@FreeBSD.org --- Comment #8 from Dimitry Andric <dim@FreeBSD.org> --- One question though: why are ports on 10.x using devel/libc++, while libc++= is in base? I would really like to understand the reasoning behind this. IIRC Baptiste added it, so I'm putting him on the CC list. Another way to fix this would be to make the ports that use devel/libc++, a= lso use devel/libcxxrt, in which this problem has already been fixed. E.g, cha= nge the devel/libc++ port so the /usr/local/lib/c++/libstdc++.so linker scripts= it installs contains: GROUP ( /usr/local/lib/libc++.so.1 /usr/local/lib/libcxxrt.so ) and add devel/libcxxrt as a dependency of devel/libc++. This is far easier than an EN, and this workaround can be removed as soon as 9.x and 10.[12] reach end of life. In fact, we should actively try to remo= ve the whole devel/libc++ and devel/libcxxrt ports in the future. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214863-29464-l5UyvSpE6A>