https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215193
--- Comment #16 from Mark Millard <marklmi26-f...@yahoo.com> --- (In reply to Gleb Popov from comment #10) QUOTE Putting USE_GCC=yes into a port makes it link to libstdc++. END QUOTE It makes the default for g++'s -stdlib=??? be -stdlib=libstdc++ but it still allows an explicit -stdlib=libc++ instead. By contrast, no FreeBSD clang++ is configured to use libstdc++ ever, even if -stdlib=libstdc++ is on the command line. At least, that I how I remember the behavior. Note that g++ used not-allow/not-follow -stdlib=libc++ until Jan changed it: author Jan Beich <jbe...@freebsd.org> 2022-08-20 16:06:02 +0000 committer Jan Beich <jbe...@freebsd.org> 2022-08-25 21:35:37 +0000 commit 86e7abbbf467e97ffa58363ca3327d08395931ee (patch) tree fc3fd7345bd1631c3f4ac1703c88e39bc90800a2 /lang/gcc12 parent 65fe81d73e72f1303557c9809a73716cc7fcd77b (diff) lang/gcc12: Expose non-default -stdlib=libc++ support Fix -stdlib=libc++ option which produced "error: unrecognized command-line option '-stdlib=libc++'". PR: 265962 Approved by: salvadore (maintainer) Exp-run by: antoine (via bug 265964) -- You are receiving this mail because: You are the assignee for the bug.
