[ELDK] glibc change for eldk 3.1.1
Levend Sayar
levend.sayar at karel.com.tr
Fri Mar 26 14:20:58 CET 2010
Hi,Detlev,
> Ok, I'm getting lost here. Threads are per definition defined on a
> process basis. pthread_mutex is also a construction which I fail to see
> how to share it between processes. Can you show me exactly what you
> want to do here?
I aggree with you. AFAIK, mutexes are in fact intra process primitives. But I dont understand why BerkeleyDB says these log lines
although
we have "pthread_mutex_init" function in our ELDK 3.1.1 toolchain.
bdb(dc=karelarge,dc=com): unable to initialize mutex: Function not implemented
bdb(dc=karelarge,dc=com): PANIC: Function not implemented
bdb(dc=karelarge,dc=com): unable to join the environment
------------------------------------------------------------------------------------------------------
> Well interprocess synchronization is _per definition_ outside of threads
> as the latter are defined on a process basis. For interprocess
> communication we have other primitives like SysV IPC, shared memory,
> etc.
Exactly, semaphores for example
------------------------------------------------------------------------------------------------------
>Can you show me such a wording? This would be news to me.
BerkeleyDB source code has a comment like this :
"Currently we support one kind of mutex that is intra-process only,
POSIX 1003.1 pthreads, because a variety of systems don't support
the full pthreads API, and our only alternative is test-and-set."
So I thought there is something in the standart like inter process mutex.
------------------------------------------------------------------------------------------------------
> I do not understand what you are doing here, sorry.
I want to show you the alternatives for mutex implementation that BerkeleyDB can use. Maybe someone will
say "You have to choose this one"
_lvnd_
(^_^)
More information about the eldk
mailing list