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)
Nicolas Lehuen

2005-09-13, 5:52 pm

I'm sure it is required, even after fixing the S in APR_HAS_THREADS I tried
with and without the PyEval_AcquireLock code and the latter works while the
former doesn't. I don't know why though... I'll have to review the code once
more to understand.

Regards,
Nicolas

2005/9/13, Gregory (Grisha) Trubetskoy <grisha@apache.org>:
>
>
> 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:
>
> threading
> when
> install
> or
> on
> preserve
> unit
> http://svn.apache.org/viewcvs.cgi/h...06619&r2=125771
> our
> so
> apr_thread_mutex_create(& interpreters_lock,APR_THREAD_MUTEX_UNNES
TED,p);
> (or
> to
> the
> answer,
> all,
> threads,
> code
> This
> have
> is
> in
> If
> with
> nicolas.lehuen@gmail.com
> assumes
> functions
> my
> in
> apr_thread_mutex_create(& interpreters_lock,APR_THREAD_MUTEX_UNNES
TED,p);
>


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com