Any thoughts on this issue? Pointers to what might be the culprit(s)?


-----Original Message-----
From: Schmoll, Brett x66244
Sent: Monday, June 12, 2006 2:28 PM
To: 'Jean-frederic Clere'
Cc: ''
Subject: RE: decision on anonymous shared memory allocation method

ezmlm-reject: fatal: Sorry, I don't accept messages larger than 100000 bytes (#5.2.3)

Log is 111k and was bounced from the list....any particular portion that would be useful?


-----Original Message-----
From: Jean-frederic Clere []
Sent: Monday, June 12, 2006 2:00 PM
To: Schmoll, Brett x66244
Subject: Re: decision on anonymous shared memory allocation method

Schmoll, Brett x66244 wrote:

> Hi all,
> Trying to see if I can get svn to build on our HP NonStop platform and
> am having some difficulties getting APR portion to build.
> Checking for Shared Memory Support...
> checking for library containing shm_open... no
> checking sys/mman.h usability... no
> checking sys/mman.h presence... no
> checking for sys/mman.h... no
> checking sys/ipc.h usability... yes
> checking sys/ipc.h presence... yes
> checking for sys/ipc.h... yes
> checking sys/mutex.h usability... no
> checking sys/mutex.h presence... no
> checking for sys/mutex.h... no
> checking sys/shm.h usability... yes
> checking sys/shm.h presence... yes
> checking for sys/shm.h... yes
> checking sys/file.h usability... no
> checking sys/file.h presence... no
> checking for sys/file.h... no
> checking kernel/OS.h usability... no
> checking kernel/OS.h presence... no
> checking for kernel/OS.h... no
> checking os2.h usability... no
> checking os2.h presence... no
> checking for os2.h... no
> checking for mmap... no
> checking for munmap... no
> checking for shm_open... no
> checking for shm_unlink... no
> checking for shmget... yes
> checking for shmat... yes
> checking for shmdt... yes
> checking for shmctl... yes
> checking for create_area... no
> checking for MAP_ANON in sys/mman.h... no
> checking for /dev/zero... no
> ./configure:Error: decision on anonymous shared memory allocation
> method failed
> Given the yes's on shmget etc I would have thought that it wouldv'e
> worked. Is their anyway to work-around this and/or fix it?
You should have a config.log somewhere please send it.



> -Brett Schmoll
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and
> confidential. If the reader of the message is not the intended
> recipient or an authorized representative of the intended recipient,
> you are hereby notified that any dissemination of this communication
> is strictly prohibited. If you have received this communication in
> error, please notify us immediately by e-mail and delete the message
> and any attachments from your system.