From: Eugen D. <Eug...@pu...> - 2011-07-30 09:54:42
|
On 29/07/11 23:48, Stephen Kitt wrote: > Hello everyone, > > I'm late to the party, and replying to an older email than the end of the > thread, but I'll try to answer the remaining questions. > > On Fri, 22 Jul 2011 15:55:53 +0200, Eugen Dedu > <Eug...@pu...> wrote: >> On 22/07/11 15:38, Ozkan Sezer wrote: >>> On Fri, Jul 22, 2011 at 4:16 PM, Eugen Dedu >>> <Eug...@pu...> wrote: >>>> I have a big linux application and I use mingw to build it for windows >>>> too. When I use mingw32 everything goes well, but when I use mingw-w64 >>>> in 32bit mode and execute it on Windows I receive the error: application >>>> has not been initialised correctly, error 0xc0000142. I looked on >>>> Internet, but nothing is useful (one page >>>> http://support.microsoft.com/kb/838857 told that this is an error on >>>> rights or some files, but the same application built with mingw32 works, >>>> so there must be other thing). What have I missed? >>> >>> If it is a c++ app, make sure that libgcc_s_sjlj-1.dll is on your PATH >>> )or put it in the same directory as your exe.) >> >> It is a c++ application. I do not find this file on my machine. >> Stephen, is this file the same as >> gcc-mingw-w64: /usr/lib/gcc/i686-w64-mingw32/4.6/libgcc.a >> ? Could the .dll be included in debian package? > > As Ruben pointed out, the Debian mingw-w64 packages currently disable shared > libraries, so there no DLL is required here. I'm working on supporting shared > libraries, their lack shouldn't prevent a successful Ekiga build... > > Concerning the package structure, they're currently split only by source (so > binutiles, gcc and mingw-w64), with dependencies on existing packages for > duplicate files (libstdc++6-4.6-dev for C++ headers for example). > > Ruben, I'm not sure from your emails to the thread whether you've identified > configure flags I should use but don't, or whether your last comment means > that the flags you thought were missing are actually there. If there are > missing flags (which is definitely possible), would you mind telling me which > ones? > > Eugen, did you try your Ekiga build with one of the builds Ruben suggested? Hello Stephen, glad to see you back :o) I have not tried, since I fear it will take me too much time, so I prefered to wait your answer. > Also, could you tell me what changes you made to the Ekiga build to have it > work with mingw-w64 (well, build at least)? I've made the obvious changes to > the man Makefile, but ptlib's build fails with Use the Makefile attached in a new directory and execute: make BIT32=1 update-sources remove "-avoid-version" from src/opal/plugins/configure.ac make BIT32=1 This will take stable branches, not release, which is better since after the release I made 2-3 fixes in ptlib/opal for mingw-w64 (probably because the compiler is more strict). If you still have errors (you should not), e-mail me. Oh, and I forgot... There were two mingw-w64 errors, fixed upstream a few days ago, and you need to use them before compiling: - create a link libvwf32.a to libmsvwf32.a (http://sourceforge.net/tracker/?func=detail&atid=983354&aid=3374153&group_id=202880) - there was an error on assertions, I fixed it manually (https://sourceforge.net/tracker/?func=detail&atid=983354&aid=3373905&group_id=202880) Please tell me if it is too complicated... And a question: in the Makefile attached, line 23 there is: export DEB_HOST_GNU_TYPE:="i586-pc-mingw32" Should it be changed to i686-pc-mingw32 for mingw-w64 32 bit and to x86-64-pc-mingw64 for 64 bit? -- Eugen |