Sebastian Bauer

Like any similar error this is most likely the result of the respective c libraries not implementing these functions. Please check, if these functions exist within the library. Only if...

It depends ;) I recall that even if some functions are present a similar function may be missing and thus the configure stage of libstdc++ may disable a whole family...

I cannot test myself, but @salass00 did a fix elsewhere, maybe it will fix this problem as well. For people that have running machines it is easy to test, just...

> @sba1 > Sorry forgot to ask, but will you in interest if I will gift you real hardware? You are the one who deserve it, so if you need...

> I did a little bit research and it seems that there has been issues with GNU's std::call_once implementation and they have actually fixed it recently for Linux: https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=93e79ed391b9c636f087e6eb7e70f14963cd10ad Yes,...

If the libstdc++ implementation of call_once really plainly uses the gthread without propagating exceptions properly through the c function then it cannot work as well as it is not exception-safe...

Am 2019-01-18 08:25, schrieb ksdhans: > Compiling with -athread=pthread results in a "cannot find > gthr-amigaos-pthread.o" error (with gcc 8.1.0 build 20181211-695) Only native is supported for now. The pthread...

Am 2020-04-13 00:14, schrieb Chris Charabaruk: > Sometimes when building, the cc1 process of GCC will crash, seemingly > at random. It's happened to me on the most basic C...

Am 2018-11-10 16:32, schrieb JosteinAarb: > As the cpu architecture of my X5000 (e5500) supports CPU instructions > like ISEL, which will be beneficial for the performance, I want to...

Am 2019-02-07 10:04, schrieb kas1e: > @hans [1] > Maybe that is problems with native builds from the bintray.com, but i > build myself latest version from adtools on cygwin,...