Date: Thu, 30 Jan 2025 00:06:26 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 284378] www/webkit2-gtk: interactions with C++ dependencies built with clang/libc++ causes WebProcess crash Message-ID: <bug-284378-6497-5YxuDl3A9i@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-284378-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-284378-6497@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=3D284378 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #29 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Nuno Teixeira from comment #1) (In reply to Charlie Li from comment #2) (also: huanghwh@gmail.com ) lang/gcc* for a modern enough * supports use of -stdlib=3Dlibc++ instead of the gcc default of -stdlib=3Dlibstdc++ . In other words, lang/gcc14 (for example) supports using the system's libc++ instead of the lang/gcc* 's libstdc++ . This gets rid of the problem of using contradictory implementations of the C++ standard library in the same process. So, if you can figure out how to have the relevant package(s) build using -stdlib=3Dlibc++ consistently with gcc, you have a chance of it building based on the system libc++ and mixing with other things better. (I've no clue if the implementation is generic with respect to the C++ standard library vs. being tied to a specific implementation.) In some cases, this might be easier than switching from lang/gcc* to system clang (or to a devel/llvm* clang). At least something to explore to see if it helps. --=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-284378-6497-5YxuDl3A9i>