Re: [Mingw-w64-public] Compilation of GCC from svn
No clue about MSYS but I build off the GCC 5 git branch under MSYS2 without any issues pretty easily. On Sun, Aug 9, 2015 at 6:02 AM, Javier Jaramago Fernandez wrote: > Hi there! Thanks you so much for taking the time of attending me. I have > been trying for several hours to compile the SVN version of the GCC using > MinGW64 (last dongsheng-daily) without succeed. The reason i want to, its > because a new feature has been added to GCC in the past days, and that > version doesn't include it. How do you make those daily builds? Do you have > any special tutorial or requirements? My current setup includes MinGW64 and > MSYS with all the utilities that GCC needs as prerequisites including Flex > and Bison because it's the development version, am i missing something? > > Thanks you so much. Best regards. > > > -- > Javier Jaramago Fernández. > > -- > > ___ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread
7 aug 2015 kl. 14.50 skrev Rainer Emrich : > This fixes the issue, libgom.sum attached. Can we have this in head and in > 4.x ? That is probably the expedient solution even if we eventually get libgomp fixed. (The patch adds an extra cycle or two on some critical paths but I suppose we can live with that.) >> Fixing libgomp is probably cleaner: either make sure the constructors are >> run in the right order or initialize the acc_device_lock mutex statically. > > Are you willing to work on this? I can't, I don't have the skills. It looks quite straightforward actually, but probably better done by the libgomp maintainers upstreams. A GCC bug has been filed: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67141 -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] Compilation of GCC from svn
Hi there! Thanks you so much for taking the time of attending me. I have been trying for several hours to compile the SVN version of the GCC using MinGW64 (last dongsheng-daily) without succeed. The reason i want to, its because a new feature has been added to GCC in the past days, and that version doesn't include it. How do you make those daily builds? Do you have any special tutorial or requirements? My current setup includes MinGW64 and MSYS with all the utilities that GCC needs as prerequisites including Flex and Bison because it's the development version, am i missing something? Thanks you so much. Best regards. -- Javier Jaramago Fernández. -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] ./configure - and mingw-w64 confusion
On Sat, Aug 8, 2015 at 8:37 PM, Duane Ellis wrote: > > It's built from this project (and branch, be careful to not use > master!) on github: > https://github.com/Alexpux/mingw-builds/tree/develop but as I say, you > want canadian cross, and well, I'll not repeat what I wrote before, > I'd just encourage you to read it carefully. > > > Actually Python just needs to be cross compiled in this case. It might > work from mingw-builds, but likely not. > > > > That is _THE_ problem, python generally *blocks* all cross compilation the > example is here: > > https://github.com/python/cpython/blob/master/configure.ac#L377 > > Where the “configure” script specifically blocks this. > > yea, I could undo this - and let this pass - but they have or had a very > specific reason to block this > > I don’t know what that reason is, could it be > > “it will not work - thus we block it" > > Or > “I don’t know if it will - so we block it” > > There is no indication behind the reasoning. > CPython can't be compiled to run on Windows using anything other than MSVC without *major* changes. You could undo this first stumbling block that you ran into but then you'd need to fix the 80-odd other things that you'll run into after that which we've fixed up at: https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-python2 https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-python3 > -Duane. > > > -- > > ___ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public