I prefer MinGW-64 too.
2012/9/26 Ruben Van Boxem
> If I may have a say in Qt's decision on a toolchain, I'd suggest using
> MinGW-w64 exclusively.
--
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
-
Hi niXman, no it won't cause a link error because the #pragma just
gets ignored so essentially there is no parallelism, hence, no hang.
It is interesting though that when using -fopenmp, the -lpthread flag
is unnecessary. Maybe when using openmp links some other version of
pthread somehow?
Just fo
2012/9/12 Antony Riakiotakis:
> Hi, any news on this issue? Can I help in some way?
Hi Antony,
I want to pay your attention to the fact that if I compile the code
without using the '-fopenmp' option, then the bug does not occur.
Although, far as I remember in this case must occur a link error. Bu
2012/9/26 Koehne Kai
> Hi all,
>
> I wrote a while ago that 'I haven't found a stock native MinGW 64 bit
> package yet that can compile Qt 5 + Qt Creator.' And since I get cited on
> this I guess it's time to correct it :)
>
> Thanks to personal efforts of various people both on the Qt side (name
Hi all,
I wrote a while ago that 'I haven't found a stock native MinGW 64 bit package
yet that can compile Qt 5 + Qt Creator.' And since I get cited on this I guess
it's time to correct it :)
Thanks to personal efforts of various people both on the Qt side (namely
Jonathan Liu), as well as on
2012/9/26 Christer Solskogen
> Ruben Van Boxem writes:
>
> >
> > Hi everyone,I am in the process of uploading a GCC 4.8 experimental
> build fo
> > 64-bit Windows.
>
> I tried it after I used my own toolchain. The thing that I noticed is that
> both
> your toolchain(cc1.exe) and mine crash when
Ruben Van Boxem writes:
>
> Hi everyone,I am in the process of uploading a GCC 4.8 experimental build fo
> 64-bit Windows.
I tried it after I used my own toolchain. The thing that I noticed is that both
your toolchain(cc1.exe) and mine crash when compiling Boost. That is something
that the G
