apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ed Holyat <ehol...@OLF.COM>
Subject RE: Solaris 2.8 and apr_global_mutex... head of branch
Date Fri, 21 May 2004 18:55:43 GMT
Sorry about the misunderstanding on my part.  
It is only the apr_global_mutex_trylock that is not implemented on the
Unixes.  
Which happens to be what I was trying to use.  
Any updates on where this part of the API stands, It is available on the
win32 side.  


#0  proc_mutex_no_tryacquire (new_mutex=0x3d678) at
locks/unix/proc_mutex.c:29
#1  0xff2c17b8 in apr_proc_mutex_trylock (mutex=0x3d678) at
locks/unix/proc_mutex.c:827
#2  0xff2c0a8c in apr_global_mutex_trylock (mutex=0x3d668) at
locks/unix/global_mutex.c:130

-----Original Message-----
From: Jeff Trawick [mailto:trawick@attglobal.net]
Sent: Thursday, May 20, 2004 6:16 PM
To: dev@apr.apache.org
Subject: Re: Solaris 2.8 and apr_global_mutex... head of branch


Ed Holyat wrote:
> 	Is the apr_global_mutex.. api available for Solaris and Linux?

sure; APR won't build without selecting and calling some native system 
primitive for that

> 	For me, the apr status is returning that apr_global_mutex_.. is not
> implemented on solaris2.8, redhat 2 and 3 enterprise.


What is the call to apr_global_mutex_...?

what does strace or truss of the program calling it show?

for Linux, is your setting (or un-setting) of LD_ASSUME_KERNEL environment 
variable the same for apr configure time as at application run time?

	I am assuming that
> it should be, in which case, the problem is in buildconf or libtool
version
> 1.5.6.

I don't see how libtool would affect that, but if you are suspicious it is
easy 
to try 1.4.3, which most(?) apr users use.


© 2004 OpenLink Financial 

Copyright in this message and any attachments remains with us.  It is
confidential and may be legally privileged.   If this message is not 
intended for you it must not be read, copied or used by you or 
disclosed to anyone else.   Please advise the sender immediately if 
you have received this message in error.

Although this message and any attachments are believed to be free of 
any virus or other defect that might affect any computer system into 
which it is received and opened, it is the responsibility of the 
recipient to ensure that it is virus free and no responsibility 
is accepted by Open Link Financial, Inc. for any loss or damage in any 
way arising from its use.



Mime
View raw message