>
> problems getting the configuration for the semaphores to work correctly
>
There really aren't a lot of configuration options any more.  I just
recently cleaned up the SysSempahore code with revision 12259.
And I now believe that we cannot run at all without both
pthread_mutexattr_settype and PTHREAD_MUTEX_RECURSIVE so I might as well
remove that option too (all of our platforms that we currently run builds
on have support for those.)

Thomas, are you at revision 12259 or later?  If not can you please update?

The last time you reported the CMake status of the various pthread
functionality, you showed some "failed"
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_mutexattr_settype
-- Looking for pthread_mutexattr_settype - not found
-- Looking for pthread_mutex_timedlock
-- Looking for pthread_mutex_timedlock - not found
-- Performing Test HAVE_PTHREAD_MUTEX_ERRORCHECK

*-- Performing Test HAVE_PTHREAD_MUTEX_ERRORCHECK - Failed *-- Performing
Test HAVE_PTHREAD_MUTEX_RECURSIVE
-- Performing Test HAVE_PTHREAD_MUTEX_RECURSIVE - Failed
What's the current status?

To test the actual mutex functionality on Android, can you compile and run
this test?
https://android.googlesource.com/platform/system/extras/+/froyo/tests/bionic/libc/bionic/test_mutex.c
Please also test whether " #define __USE_UNIX98 1" is required to
successfully compile/run.
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to