Hi, A small update as follows: I have updated the environmet, and it seems to be working, so the next nightlies wil have a new gcc for x86_64. It seems that msys2 does not have an up to date version of gcc for i686. I guess they may be having some build issues. I didn't invenstigate it. So currently we are using:
mingw-w64-i686-gcc 7.3.0-2 mingw-w64-x86_64-gcc 8.2.0-3 Regards Nick ØstergaardHi On Sun, 28 Oct 2018 at 21:26, Nick Østergaard <oe.n...@gmail.com> wrote: > > From https://bugs.launchpad.net/kicad/+bug/1800339/comments/9 > > It do indeed seem like updating the msys2 build environment is a good > idea. I created a new environment, but at the moment I am having a > little troble with make the new one work. Maybe there is some > environment varible that I have forgotten. I will change it over as > soon as possible for the future builds. > > Nick > On Sun, 28 Oct 2018 at 01:12, Nick Østergaard <oe.n...@gmail.com> wrote: > > > > Hi Seth, > > > > Currently the gcc version is: > > mingw-w64-i686-binutils 2.28-2 > > mingw-w64-i686-gcc 7.1.0-3 > > mingw-w64-i686-gcc-ada 7.1.0-3 > > mingw-w64-i686-gcc-fortran 7.1.0-3 > > mingw-w64-i686-gcc-libgfortran 7.1.0-3 > > mingw-w64-i686-gcc-libs 7.1.0-3 > > mingw-w64-i686-gcc-objc 7.1.0-3 > > mingw-w64-x86_64-binutils 2.28-2 > > mingw-w64-x86_64-gcc 7.1.0-3 > > mingw-w64-x86_64-gcc-ada 7.1.0-3 > > mingw-w64-x86_64-gcc-fortran 7.1.0-3 > > mingw-w64-x86_64-gcc-libgfortran 7.1.0-3 > > mingw-w64-x86_64-gcc-libs 7.1.0-3 > > mingw-w64-x86_64-gcc-objc 7.1.0-3 > > > > I can try to upgrade in the weekend in another env such that we can > > retest if it makes a difference. > > > > Nick > > On Sat, 27 Oct 2018 at 03:34, Seth Hillbrand <s...@hillbrand.org> wrote: > > > > > > Hi Devs- > > > > > > Does anyone know what our mingw64 g++ version for the nightly builds' > > > support for C++11 is? There are a few bug reports of odd locking > > > behavior[1][2]. These seem to be when the user gets to the dynamic > > > ratsnest update. > > > > > > So, thinking that our use of atomic might be problematic, I've adjusted > > > this a few times, finally going to std::async with std::futures > > > promises. This seems to have cleared the issue for [1] but made [2] > > > worse. > > > > > > Both std::async and std::future have been supported on Linux gcc since > > > at least 4.7 but I've read in a few places [3][4] that it might not work > > > in mingw64. I can't seem to find a list of supported features anywhere. > > > Does anyone have a reference? > > > > > > -Seth > > > > > > [1] https://bugs.launchpad.net/kicad/+bug/1795951 > > > [2] https://bugs.launchpad.net/kicad/+bug/1798460 > > > [3] > > > https://stackoverflow.com/questions/10209871/c11-stdasync-doesnt-work-in-mingw > > > [4] https://github.com/meganz/mingw-std-threads/issues/17 > > > > > > _______________________________________________ > > > Mailing list: https://launchpad.net/~kicad-developers > > > Post to : kicad-developers@lists.launchpad.net > > > Unsubscribe : https://launchpad.net/~kicad-developers > > > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp