[Mingw-cross-env-list] MinGW glib threading issues?

[Matthias Gehre]

Hello list,

first I want to thank your for that great software, mingw-cross-env
was really painless to setup, and I could add two
packages (llvm & libxml++) right away without hassle. I really look
clean and well designed.

I'm currently trying to port lightspark
(http://lightspark.github.com/) to win32 with the help of current
mingw-cross-env from hg.
I found different informations on the net regarding bugs with
exception handling and threading, but I don't know if that is
outdated yet. Are there issue I have to watch for?

With the crosscompiled binary of lightspark, I see (both on wine and
native win32) spontanous hangs and the inability to use gdb on them.
(mingw-cross-env's gdb does not work under my vanilla 1.3 wine (just
hangs on any command such as 'run' or 'quit'; under native win32
I cannot use ctrl-c to break on the console; under native win32
eclipse, gdb can be used until that spontanous hang occurs, afterwards
it does not regain control ).

I saw that glib is compiled with --disable-threads (in src/glib.mk).
Does that mean I cannot use glibs thread/mutex etc primitives?
Lightspark depends heavily on those.

I also read that mingw's gcc needs '-mthreads' on every sourcefile if
one uses threads. What exactly does that do? Is it enough to
compile my own application with '-mthreads'? Are the mingw-cross-env
packages compiled with '-mthreads'?

Thanks for your good work!

Best wishes,
Matthias