On Tue, Aug 22, 2023 at 8:32 PM James Almer <jamr...@gmail.com> wrote:
> > >>> > >> > > "mem.h"->"avutil.h"->"common.h"->"<stdlib.h>"->"<sys/types.h>"->"<bits/pthreadtypes.h>" > >> > >> Why would bits/pthreadtypes.h be available if there's no pthreads? > >> > > I guess it is related to POSIX. If you check <sys/types.h>, you will find > > the following code: > > > > /* Now add the thread types. */ > > #if defined __USE_POSIX199506 || defined __USE_UNIX98 > > # include <bits/pthreadtypes.h> > > #endif > > Well, not all targets are POSIX. If you look at the win32 and os/2 > wrappers, they need to define pthread_t. So it's not guaranteed to be > defined when !HAVE_THREADS. > Done by v5 > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
