![](https://secure.gravatar.com/avatar/e334895d477b1d0d47e0d9d276fa3f80.jpg?s=120&d=mm&r=g)
Did you try the gcc 4.7 with the sjlj stack from TDM?
Adib.
On Tue, Nov 13, 2012 at 8:49 PM, mathog <mathog@...1176...> wrote:
OK, will fall back to previous mingw.
On 13-Nov-2012 11:26, the Adib wrote:
Hello, please note: you must not use the original mingw from sourceforge but the TDM-port. See: http://wiki.inkscape.org/wiki/index.php/Win32Port
The difference is the stack model; we use TDM-gcc sjlj whereas the original gcc use the dw2 model.
You can only link libraries using same model.
Except that has never been the case in my experience. I have always used the mingw from sourceforge and it has worked fine. (Well, except until the Mingw upgrade that brought in the 4.7.2 compiler.) In build.xml there is a reference to an ligcc_s_sjlj-1.dll. Other than linking to that dll, how else does the compiler know what type of exception handling to use, compiler or switch maybe?
Is it maybe the case that gcc 4.7.2 for windows finally changed from sjlj to dw2 exception handling and that is what is breaking things?
Thanks,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech