Ahh, that makes a little more sense. Yes, you will almost surely
want to rebuild the mingw-runtime package to suit this new compiler
configuration, since it does appear to be incompatible. Based on
everything we know so far, that would explain why the 'upstream'
binary is ok now but the one in t
Ron wrote:
On Sat, Jan 29, 2005 at 03:45:33PM +0800, Paul wrote:
by the way, i found the mingwm10.dll was faulty under linux, my apps
worked with the one distributed with the runtime from the windows
release of mingw. whats going on there?
hmm... no idea on that one, sorry -- can anyone else
On Sat, Jan 29, 2005 at 03:45:33PM +0800, Paul wrote:
> by the way, i found the mingwm10.dll was faulty under linux, my apps
> worked with the one distributed with the runtime from the windows
> release of mingw. whats going on there?
hmm... no idea on that one, sorry -- can anyone else confir
by the way, i found the mingwm10.dll was faulty under linux, my apps
worked with the one distributed with the runtime from the windows
release of mingw. whats going on there?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Thanks Paul!
I've had too much piled on to be able to test this before now, but
finding time for a new upload with this as a confirmed fix should
be much easier.
I'll get some new packages tested shortly,
cheers,
Ron
On Sun, Jan 23, 2005 at 10:08:52PM +0800, Paul wrote:
> I can confirm that up
I can confirm that updating debian/rules to include
--enabled-sjlj-exceptions fixes the throw-exception problems I have
observed.
Until a fix in the binary release is available, just apt-get source
mingw32 ... edit debian/rules to add in the configuration, and then
fakeroot debian/rules binary
6 matches
Mail list logo
