Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-03-24 Thread Alexpux
brary. here is the only error message. Try rev3. i686-4.8.2-release-win32-sjlj-rt_v3-rev3.7z Regards, Alexey. > > ===[snip] > Jim Michaels > From: Ray Donnelly > To: mingw-w64-public@lists.sourceforge.net > Sent: Thursday, March 20, 2014 2:34 AM > Subject: Re: [Mingw-w64-public]

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-03-24 Thread Jim Michaels
uot;here" who said "that" >about "it". Would it be possible for you to connect the dots please? > > >> >> ____ >> From: Kai Tietz >> To: "mingw-w64-public@lists.sourceforge.net" >> >> Sent: Thursday, February 20, 2014 1:14 AM >

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-03-20 Thread Ray Donnelly
> From: Kai Tietz > To: "mingw-w64-public@lists.sourceforge.net" > > Sent: Thursday, February 20, 2014 1:14 AM > Subject: Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler > > 2014-02-20 1:16 GMT+01:00 Ciro Cornejo : >> Seriously? !!! >&

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-03-20 Thread Jim Michaels
 but I thought that it was said here that the win32 version does not work with sjlj in a stable way - yet? > > From: Kai Tietz >To: "mingw-w64-public@lists.sourceforge.net" > >Sent: Thursday, February 20, 2014 1:14 AM >Subject:

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-02-20 Thread Kai Tietz
2014-02-20 12:47 GMT+01:00 Hannes Domani : > Hello > > Kai Tietz schrieb am 10:14 Donnerstag, 20.Februar > 2014: > >> I would advice you to look in more detail to license issues. MS >> compiler has them, and gcc & mingw(-w64) do so too. You will be >> wondering what other licenses you are using

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-02-20 Thread Hannes Domani
Hello Kai Tietz schrieb am 10:14 Donnerstag, 20.Februar 2014: > I would advice you to look in more detail to license issues.  MS > compiler has them, and gcc & mingw(-w64) do so too.  You will be > wondering what other licenses you are using for just building a simple > hello-world-application

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-02-20 Thread Adrien Nader
Hi, On Thu, Feb 20, 2014, Ciro Cornejo wrote: > Seriously? !!! > > Come on guys, this makes the compiler unusable. > > ...but as long as you're making a toy compiler, would you consider making one > that does not support pthreads and so avoids this problem? I think we will all skip the "toy" q

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-02-20 Thread Kai Tietz
2014-02-20 10:19 GMT+01:00 LRN : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > To be precise, it's a MIT license[1]. The text OP is referring to is > explained in [2]. > > [1] https://en.wikipedia.org/wiki/MIT_License > [2] > https://programmers.stackexchange.com/questions/178486/what-exact

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-02-20 Thread LRN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20.02.2014 13:14, Kai Tietz wrote: > On 2014-02-20 1:16 GMT+01:00 Ciro Cornejo wrote: >> Seriously? !!! >> >> >> >> Come on guys, this makes the compiler unusable. > > What? > >> >> >> ...but as long as you're making a toy compiler, would you

Re: [Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-02-20 Thread Kai Tietz
2014-02-20 1:16 GMT+01:00 Ciro Cornejo : > Seriously? !!! > > > > Come on guys, this makes the compiler unusable. What? > > > ...but as long as you're making a toy compiler, would you consider making > one that does not support pthreads and so avoids this problem? > Why we should make a compiler

[Mingw-w64-public] Sigh! Back To Microsoft Compiler

2014-02-20 Thread Ciro Cornejo
Seriously? !!! Come on guys, this makes the compiler unusable. ...but as long as you're making a toy compiler, would you consider making one that does not support pthreads and so avoids this problem? Thanks. Hi! Sorry for the interruption, but you may want to take at least a few seconds to loo