[Bug 221288] lang/gcc5 links against libsupc++ when compiling

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288 Rene Ladan changed: What|Removed |Added Resolution|--- |Overcome By Events

[Bug 221288] lang/gcc5 links against libsupc++ when compiling

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288 --- Comment #11 from Mark Millard --- Trying my standard-C++ program that uses C++ threads in a more modern context (head -r322287, lang/gcc7) in an amd64 context under a Virtual Box virtual machine (that is running on

[Bug 221288] lang/gcc5 links against libsupc++ when compiling

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288 --- Comment #9 from Mark Millard --- (In reply to Mark Millard from comment #6) Returning to a g++6 based a.out back trace for the C++ threading to show some infrastructure usage involved: Thread 12 received signal

[Bug 221288] lang/gcc5 links against libsupc++ when compiling

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288 --- Comment #8 from Mark Millard --- (In reply to Mark Millard from comment #7) Looking at its details bugzilla 212330 is not a good example for here in 221288. For one the failing context was armv6 and amd64 worked.

[Bug 221288] lang/gcc5 links against libsupc++ when compiling

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288 --- Comment #7 from Mark Millard --- (In reply to Mark Millard from comment #5) FYI: An older report of the threading issues with the tiny program: static void f() {} int main(int, const char* []) { auto a0{

[Bug 221288] lang/gcc5 links against libsupc++ when compiling

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288 --- Comment #6 from Mark Millard --- (In reply to Mark Millard from comment #5) To avoid confusion from a typing/editing error. . . "Note #3 -> #4 goes from" in the reference to the g++6 based a.out backtrace should

[Bug 221288] lang/gcc5 links against libsupc++ when compiling

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288 --- Comment #5 from Mark Millard --- I suspect this mix of infrastructures ties in to why standard c++ threading fails under the likes of g++6 compiles while the code works when compiled and linked via system clang++