On Sunday, 25 August 2019 01:05:23 PDT Ray Donnelly wrote:
> > > just mentioning it:
> > > https://github.com/msys2/MINGW-packages/issues/2519
> >
> > The description of the bug says "winpthreads", which means it's not MinGW,
> > it's Cygwin/MSYS2.
>
> This is completely incorrect. Thiago I would
On Fri, 23 Aug 2019, 17:11 Thiago Macieira,
wrote:
> On Friday, 23 August 2019 00:12:50 PDT Roland Winklmeier wrote:
> > Just for your awareness: There is an old bug related to thread_local in
> > MinGW which afaik was never fixed. It compiles correctly, but every
> > executable crashes during sh
On Saturday, 24 August 2019 02:21:13 PDT Konstantin Tokarev wrote:
> 23.08.2019, 21:11, "Thiago Macieira" :
> > On Friday, 23 August 2019 09:04:55 PDT Konstantin Tokarev wrote:
> >> > libgcc on pure MinGW doesn't use winpthreads, it uses Win32.
> >>
> >> std::thread and co are not implemented fo
23.08.2019, 21:11, "Thiago Macieira" :
> On Friday, 23 August 2019 09:04:55 PDT Konstantin Tokarev wrote:
>> > libgcc on pure MinGW doesn't use winpthreads, it uses Win32.
>>
>> std::thread and co are not implemented for win32, so we use pthreads version
>> in Coin and distribute it with SDK.
On Friday, 23 August 2019 09:04:55 PDT Konstantin Tokarev wrote:
> > libgcc on pure MinGW doesn't use winpthreads, it uses Win32.
>
> std::thread and co are not implemented for win32, so we use pthreads version
> in Coin and distribute it with SDK.
We don't use std::thread in Qt, so why are you t
On Friday, 23 August 2019 08:58:09 PDT Simon Hausmann wrote:
> Hi,
>
> I ran into the crash a while ago in the CI. See also
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83562 .
That last comment in the bug report seems relevant to us.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Soft
23.08.2019, 18:11, "Thiago Macieira" :
> On Friday, 23 August 2019 00:12:50 PDT Roland Winklmeier wrote:
>> Just for your awareness: There is an old bug related to thread_local in
>> MinGW which afaik was never fixed. It compiles correctly, but every
>> executable crashes during shutdown. Not
Hi,
I ran into the crash a while ago in the CI. See also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83562 .
Simon
On 23. Aug 2019, at 23:12, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
On Friday, 23 August 2019 00:12:50 PDT Roland Winklmeier wrote:
Just for your awareness: The
On Friday, 23 August 2019 00:12:50 PDT Roland Winklmeier wrote:
> Just for your awareness: There is an old bug related to thread_local in
> MinGW which afaik was never fixed. It compiles correctly, but every
> executable crashes during shutdown. Not sure if this relevant in this case,
> just mentio
Am Do., 22. Aug. 2019 um 22:47 Uhr schrieb Thiago Macieira <
thiago.macie...@intel.com>:
> On Thursday, 22 August 2019 12:05:39 PDT Danila Malyutin wrote:
> > Isn't it already the case:
> https://doc.qt.io/qt-5/supported-platforms.html
> > ?
>
> Looks like it.
>
> I'll dust-off the Q_THREAD_LOCAL
On Thursday, 22 August 2019 12:05:39 PDT Danila Malyutin wrote:
> Isn't it already the case: https://doc.qt.io/qt-5/supported-platforms.html
> ?
Looks like it.
I'll dust-off the Q_THREAD_LOCAL patch and send it off through the CI. If any
platform can't compile it, we'll just remove the platfor
Isn't it already the case: https://doc.qt.io/qt-5/supported-platforms.html
?
чт, 22 авг. 2019 г. в 18:10, Thiago Macieira :
> On Wednesday, 21 August 2019 17:17:17 PDT Kevin Kofler wrote:
> > > So let me instead change my request:
> > > Can we require GCC 8 for MinGW for Qt 5.15?
> >
> > This i
On Wednesday, 21 August 2019 17:17:17 PDT Kevin Kofler wrote:
> > So let me instead change my request:
> > Can we require GCC 8 for MinGW for Qt 5.15?
>
> This is a much more reasonable request than the original one.
>
> For what it's worth, the oldest still supported Fedora release (Fedora 29)
>
13 matches
Mail list logo