Apache Mod-Python - Re: FreeBSD compile problem (was Getting ready for 3.2 beta 2)

This is Interesting: Free IT Magazines  
Home > Archive > Apache Mod-Python > September 2005 > Re: FreeBSD compile problem (was Getting ready for 3.2 beta 2)





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: FreeBSD compile problem (was Getting ready for 3.2 beta 2)
Gregory (Grisha) Trubetskoy

2005-09-13, 5:52 pm


Good job - I've tested it and it works on FreeBSD. Just one last thing I
wanted to confirm - are you sure that PyEval_AcquireLock is required, or
was this a sideffect of the missing 'S'? I just want to make sure we're
not doing double locking where it's not needed.

Grisha

On Tue, 13 Sep 2005, Nicolas Lehuen wrote:

> OK I fixed the problem, please check again on FreeBSD. Here is what I've
> done (from the subversion comment) :
>
> "Fixed : APR_HAS_THREADS ends with an 'S'. Reintroduced the calls to
> PyEval_AcquireLock and PyEval_ReleaseLock as they are required if threading
> is enabled. Removed two debugging log entries. Added the conditional
> commenting of the LockFile directive in the LockFile class."
>
> Regards,
> Nicolas
>
> 2005/9/13, Nicolas Lehuen <nicolas.lehuen@gmail.com>:
>


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com