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 the dist is not with the new compiler package that you built.
I guess we'll need a conflict against the earlier runtime too, thanks, Ron On Sat, Jan 29, 2005 at 05:06:29PM +0800, Paul wrote: > 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 confirm this? > >it worked ok for me under wine, but I don't think I tested the last > >one on a native install. > > > >Did it fail with apps built using the compiler from the same package, > >or something else? > > > >cheers, > >Ron > > It fails with apps built from the (recompiled) debian package, with some > dlls built with debian, and some built with updated windows-mingw. > > Where does that DLL come from? Maybe I needed to rebuild it when I was > rebuilding my new mingw? I cannot be certain if it was the problem, > although I was pretty sure. I was trying to find why it was (still) > crashing, so I tried a different mingwm10.dll (from the windows dist) > and it worked... I didn't tempt fate by switching dlls again. > > It all works now, so however they build the windows dll, we should do > the same... > > thanks for the hard work Ron, > Paul > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
