Date: Mon, 07 Aug 2017 07:43:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 221288] lang/gcc5 links against libsupc++ when compiling Message-ID: <bug-221288-29464-fCYVgEi2cZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221288-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-221288-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=3D221288 David Chisnall <theraven@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |theraven@FreeBSD.org --- Comment #4 from David Chisnall <theraven@FreeBSD.org> --- (In reply to Gerald Pfeifer from comment #1) Using libstdc++ is moderately dangerous on FreeBSD, as it is not the system= C++ standard library. It is only moderately dangerous though, because it uses different symbol names for the standard library symbols and so should resul= t in a hard linker error if attempting to use it for a public interface with something linked against libc++. Using libsupc++; however, is very dangerous. It exports symbols with the s= ame names as those exported by libcxxrt. These are likely to interfere in ways that cause exciting forms of breakage. The gcc ports should not be install= ing a libstdc++ that links to libsupc++. As to clang not working with libstdc++, last time I tried it -stdlib=3Dlibs= tdc++ worked, and would pick up the correct libstdc++ if the correct -I and -L fl= ags were passed. If this doesn't work, please file a bug report. As far as I know, --gcc-toolchain is a compile-time configuration option (from the old = and now removed autoconf LLVM build system) to specify the default path for headers, not a compiler flag. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221288-29464-fCYVgEi2cZ>