Re: FreeBSD compile problem (was Getting ready for 3.2 beta 2)
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > Apache Server configuration support > Apache Mod-Python > Re: FreeBSD compile problem (was Getting ready for 3.2 beta 2)




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

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


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-13-05 10: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 threadin
g
> 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>: 
>






[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 06:26 PM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register