[Ffmpeg-devel] native win32 threads or pthreads-win32?
Thu Oct 5 09:47:14 CEST 2006
> Hmmm... Not one reply... Not even about the "unrecognized option"
> problem in gcc. Should I make a new thread about this issue without so
> many 'win32's written in the subject?
> Quoting angustia at arrozcru.no-ip.org:
>> While making the win32 builds, I came across the decision of using
>> either native win32 threads (w32thread.c), or pthreads, with the
>> pthreads-win32 library.
>> The builds at http://ffdshow.faireal.net/mirror/ffmpeg/ include
>> pthreads-win32, but I didn't get any answer from celtic druid about his
>> Are there any issues that would make me prefer one over the other, such
>> as stability or performance?
>> Also, there are two issues I would like to remember:
>> 1. Some gccs not returning error on -pthread unrecognized option.
>> M?ns, did you take a deeper look into this? I couldn't find any
>> solution, and I don't really know what other projects did about this.
>> Anything besides "don't use gcc versions x to y"?
>> 2. When mingw32 is selected (or os2, or beos), their native threads are
>> automatically used. If pthreads are also chosen, they will conflict:
>> Would it be ok to only include HAVE_W32THREADS if test "$pthreads"
>> != "yes"?
>> (configure, around line 2012).
>> I haven't tested this yet. I'll submit a patch when I get this
>> Could this also be a problem with os2 and beos when pthreads are
>> or do they not have any libpthreads?
The man gcc page says that the -pthread/-pthreads flags are machine
dependent options, needed for SPARC, PowerPC, IA-64.
I can only speak for Cygwin, but in this platform is produces a warning.
We could reduce warning verbosity by setting this flag only in the SPARC,
PowerPC, IA-64 specific sections of configure.
The man ld page says nothing about these flags, I believe the
"check_ldflags -pthreads" in configure could be removed.
I am speaking as of gcc 3.4.4 / ld 2.17.50, maybe older versions behave
More information about the ffmpeg-devel