RE: [Beepcore-c-users] BEEPD clashes in Solaris 2.6

[Guan W. L. <gua...@ap...>]

Hi=20
My mistake, you are right. It seems to work fine with the native thread
library of SUNOS instead of the POSIX thread library. Thank you.

Regards,
Guan Wee

-----Original Message-----
From: Guan Wee LOO=20
Sent: Monday, November 03, 2003 4:15 PM
To: 'William J. Mills'
Cc: bee...@li...
Subject: RE: [Beepcore-c-users] BEEPD clashes in Solaris 2.6


Hi,
Thanks for the suggestion. Now I simply use the pthread library instead
of the native thread library. However I still feel that the wrapper
codes are not really stable.=20


Guan Wee

-----Original Message-----
From: William J. Mills [mailto:wm...@es...]=20
Sent: Saturday, November 01, 2003 5:21 AM
To: Guan Wee LOO
Cc: bee...@li...
Subject: Re: [Beepcore-c-users] BEEPD clashes in Solaris 2.6


There might be a couple of different threading options on Solaris. The
code used to compile there, but I am not sure if anyone has in=20
a while.  Can you see what threading you have available and perhaps
reconfigure to native from posix threads for example?  This might solve
it.

-bill


On Fri, Oct 31, 2003 at 03:51:42PM +0800, Guan Wee LOO wrote:
> Hi,
> I  managed to compiled the BEEPCORE-c implementation and its beepd
> sample listener program (but only after disabling the logging feature,

> can anyone tell me how without doing this?).  Initially, everything=20
> seemed fine but the program hanged and crashed after about the 4th=20
> BEEP connection (from a BEEP client using the echo profile).  I am=20
> testing with the null-echo profile that comes with the samples. It=20
> seems that the problem lies with the SEM_WAIT call in the=20
> fiostate_unblock_write function (bp_fiostate.c)- it hangs at this=20
> point. I am using the libposix4 library. Is there anyone who manage to

> compile and run the samples successfully in Solaris 2.x without=20
> encountering any problem? Please let me know. Thanks.
> =20
> Regards,
> Guan Wee