OK, I've checked in a version that compiles both on at least Win32 and 
FreeBSD. I'm just testing if APR_HAS_THREAD is defined and only include the 
apr_thread_mutex_lock and unlock calls if it is defined.

Now, on minotaur, APR_HAS_THREAD is defined as 0. Does this mean that Apache
 
is not configured for threading ? Can we assume that we are in the prefork 
model if APR_HAS_THREAD==0, so that we can skip all the locking code ? 
Because that's what we do right now.

Regards,
Nicolas

2005/9/11, Nicolas Lehuen <nicolas.lehuen@gmail.com>:
> 
> Yes, this new code is something I commited on the 29/12/2004 (I used the 
> "blame" function of TortoiseSVN for that). It was a patch by Graham to fix
 
> MODPYTHON-2 <http://issues.apache.org/jira/browse/MODPYTHON-2>.
> 
> The problem is not in the patch, but rather in the fact that APR seems 
> configured without the thread support while Python is configured with thre
ad 
> support. mod_python.c assumes that is WITH_THREAD is defined, then the APR
 
> mutex functions are available, which is wrong. Maybe we should test for 
> APR_HAS_THREADS instead ? In that case, won't this cause any problems on 
> threaded platforms ?
> 
> I don't know if this is a problem specific to minotaur or to all version 
> of FreeBSD. I'm currently downloading the ISOs of FreeBSD and I'll try usi
ng 
> QEMU to run a FreeBSD setup on my computer, but that will be long and 
> troublesome. If someone has more clue on this issue, feel free to tell us 
> .
> 
> Regards,
> Nicolas
> 
> 2005/9/10, Jim Gallacher <jg.lists@sympatico.ca>: 
> 3.2. 
>

[ Post a follow-up to this message ]