----- Original Nachricht ---- Von: Jeff Johnson <n3...@mac.com> Betreff: Re: Compilation errors for QNX640 due to __mutex_lock > > On Mar 20, 2009, at 4:47 AM, Michael Baudisch wrote: > > > In file db/dbinc/mutex.h there are defines for > > __mutex_lock(a,b,c) and > > __mutex_unlock(a,b,c). > > > > Unfortunatly, for QNX640 there are conflicting QNX-defines in /usr/ > > qnx640/target/qnx6/usr/include/pthread.h. In QNX632 these defines > > are not in the pthread-header! > > > > So the best is I think one may be this to add the following at line > > #86 (in top of the final else of mutex-switches) in db/dbinc/mutex.h: > > #if defined(__QNXNTO__) [...] > > #endif > > > > I've added the path on HEAD and the rpm-5_1 branch of rpm cvs. > > Note that the patch is almost certainly going to get blown away > when internal Berkeley DB is upgraded down the road. Apologies > for losing the patch in advance ;-) > > A permanent solution should be attempted with QNX <-> Berkeley DB. > All that RPM with internal Berkeley DB can attempt to do is keep track > of the band-aids. > > Thanks for the patch. > > 73 de Jeff [...]
Hmmm, I see it's a temporary workaround. The problem is really caused as QNX introduced this conflicting define. Any idea how to solve this in a pleasant, lasting way? Best regards, Michael -- Michael Baudisch ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
