On Fri, Feb 18, 2011 at 4:55 PM, David Schleef <firstname.lastname@example.org>
On Fri, Feb 18, 2011 at 03:47:59PM -0500, Leo Izen wrote:You should be using the win32 async code on Windows. srsly.
> I'm getting pthread linker errors when building libschroedinger for mingw32.
> This is my configure line:
> ./configure --with-thread=pthread --with-gnu-ld --disable-gtk-doc
> --enable-static --disable-shared --host=x86_64-w64-mingw32
> I'm not using --with-thread=win32 because my frontend uses pthreads. I don't
> want any type of answer even remotely close to "use win32 threads." I'm
> using pthreads. Period.
>.< I just said don't say that. The reason I'm using pthreads is for ffmpeg. FFmpeg can use either pthreads or win32 threads. However, some programs only compile with pthreads support under mingw32 such as xvidcore, faac, and others, and If I compile FFmpeg with win32threads support and link it to a library with only pthreads support multi-threading becomes disabled for that external library. This means that if I set everything to use pthreads in order to make everything multithreaded.
So... could I please get some help, not a "don't do that" statement?
P.S. I've seen this error with x264 also when using pthreads under mingw. This might be mingw adding that. I'll have to look into that.