(In reply to Rene Dudfield from comment #0)
> Using tip(d08f9559922f) on CentOS 5, pthreads support is not detected by the
> configure script.
> 
> "checking for pthreads... no"

Well, we need at least your config.log to understand the issues.

Ugh.. nasty copy/paste typo from 5395 fix. Fixed by
https://hg.libsdl.org/SDL/rev/f60231cbd8cd

Thanks :)

Sorry to do this... but I get another compile issue:

/sdl_build/SDL2-2.0.12/src/core/linux/SDL_threadprio.c: In function ‘rtkit_initialize_realtime_thread’:
/sdl_build/SDL2-2.0.12/src/core/linux/SDL_threadprio.c:106:51: error: ‘SCHED_RESET_ON_FORK’ undeclared (first use in this function)
     int nSchedPolicy = sched_getscheduler(nPid) | SCHED_RESET_ON_FORK;
                                                   ^
/sdl_build/SDL2-2.0.12/src/core/linux/SDL_threadprio.c:106:51: note: each undeclared identifier is reported only once for each function it appears in
make: *** [build/SDL_threadprio.lo] Error 1
make: *** Waiting for unfinished jobs....



SCHED_RESET_ON_FORK ancient... and is on the host.

From the configure...

checking for pthreads... yes
checking for recursive mutexes... yes
checking for pthread semaphores... yes
checking for sem_timedwait... yes
checking for pthread_np.h... no
checking for pthread_setname_np... no
checking for pthread_set_name_np... no

I've attached the configure.log

Created attachment 4578 [details]
config.log

I'm not sure if this will be useful, but here's how to reproduce with a docker based build.

git clone https://github.com/pygame/pygame.git
git checkout sdl2.0.14-test
cd buildconfig/manylinux-build
make base-image-manylinux-x86 wheels-manylinux-x86


To get a shell on there.
    docker run --name manylinux1_base_i686 -it pygame/manylinux1_base_i686

To copy the config.log file off there into a SDL2-2.0.12/config.log locally:

    docker run pygame/manylinux1_base_i686 tar -c -C /sdl_build SDL2-2.0.12/config.log | tar x

Pushed https://hg.libsdl.org/SDL/rev/58c41548a7d4  to fix
your SCHED_RESET_ON_FORK issue: SCHED_RESET_ON_FORK is in
kernel >= 2.6.32. Don't honestly know how the result will
be at run time if built on such an old system.

Closing as fixed.

Thank you very much Ozkan :)