You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apr.apache.org by Justin Erenkrantz <je...@ebuilt.com> on 2001/07/05 02:06:40 UTC

Re: cvs commit: apr/build apr_common.m4

On Thu, Jul 05, 2001 at 12:02:10AM -0000, trawick@apache.org wrote:
> trawick     01/07/04 17:02:10
> 
>   Modified:    .        configure.in
>                build    apr_common.m4
>   Log:
>   Stop trying to provide cross-process pthread mutexes on systems where
>   the form of shared memory used with this code isn't available.
>   
>   This gets APR_HAS_PROC_PTHREAD_SERIALIZE set to 0 on (at least) HP-UX
>   and OS/390.

I have a feeling if we get true shmem working in APR (as Ian just posted
about), then this problem goes away, right?  -- justin


Re: cvs commit: apr/build apr_common.m4

Posted by Jeff Trawick <tr...@attglobal.net>.
Justin Erenkrantz <je...@ebuilt.com> writes:

> On Thu, Jul 05, 2001 at 12:02:10AM -0000, trawick@apache.org wrote:
> > trawick     01/07/04 17:02:10
> > 
> >   Modified:    .        configure.in
> >                build    apr_common.m4
> >   Log:
> >   Stop trying to provide cross-process pthread mutexes on systems where
> >   the form of shared memory used with this code isn't available.
> >   
> >   This gets APR_HAS_PROC_PTHREAD_SERIALIZE set to 0 on (at least) HP-UX
> >   and OS/390.
> 
> I have a feeling if we get true shmem working in APR (as Ian just posted
> about), then this problem goes away, right?  -- justin
> 
one would certainly hope so :)

I'd hack something simple in the meantime using another mechanism
but...

. for OS/390, I hear that SysV sem is the way to go so no hurry there...

. I have no idea how important it is to have
  APR_HAS_PROC_PTHREAD_SERIALIZE on HP-UX...

. I don't know of any other systems in this situation

-- 
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...