[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2023-01-04 Thread i.nixman at autistici dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 --- Comment #8 from niXman --- (In reply to Jonathan Wakely from comment #7) > Probably a dup of PR 108225 i.e. expecting --enable-threads=win32 to provide > std::mutex without _WIN32_WINNT >= 0x0600 yep, sure! > But it isn't provided,

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2023-01-04 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 --- Comment #7 from Jonathan Wakely --- Probably a dup of PR 108225 i.e. expecting --enable-threads=win32 to provide std::mutex without _WIN32_WINNT >= 0x0600 But it isn't provided, because the win32 model doesn't support C++11 threading for

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2023-01-04 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2023-01-04 Ever confirmed|0

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2022-12-26 Thread i.nixman at autistici dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 --- Comment #6 from niXman --- (In reply to niXman from comment #5) > (In reply to niXman from comment #4) > > (In reply to nightstrike from comment #2) > > > Is this before or after this patch set was applied? > > > > > >

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2022-12-26 Thread i.nixman at autistici dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 --- Comment #5 from niXman --- (In reply to niXman from comment #4) > (In reply to nightstrike from comment #2) > > Is this before or after this patch set was applied? > > > > https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609116.html

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2022-12-26 Thread i.nixman at autistici dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 --- Comment #4 from niXman --- (In reply to nightstrike from comment #2) > Is this before or after this patch set was applied? > > https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609116.html I think it can be so because of unspecified

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2022-12-26 Thread i.nixman at autistici dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 --- Comment #3 from niXman --- (In reply to cqwrteur from comment #0) > /home/cqwrteur/toolchains_build/gcc/libstdc++-v3/src/c++20/tzdb.cc:565:5: > error: 'mutex' does not name a type; did you mean 'minutes'? > 565 | mutex infos_mutex; >

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2022-12-26 Thread nightstrike at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 nightstrike changed: What|Removed |Added CC||i.nixman at autistici dot org,

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

2022-12-23 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 cqwrteur changed: What|Removed |Added CC||unlvsur at live dot com --- Comment #1 from