Re: scm_mutex_lock and scm_mutex_unlock

[Michael Tuexen]

Hi Marius,

see my comments in-line.

Best regards
Michael

On Oct 23, 2005, at 22:13 Uhr, Marius Vollmer wrote:

> Michael Tuexen <address@hidden> writes:
>
> > eval.c:2658: error: `PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP'
> > undeclared  here (not in a function)
> >
> > Any idea, how to fix that? I'm trying to compile it on Mac OS X 
> > 10.3.9.
>
> Hmm.  PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP seems not to be portable
> enough.  (I know that the _NP suffix means 'non-portable'...)
>
> I guess the most portable way to get recursive mutexes is to use
> pthread_mutex_init together with pthread_mutexattr_settype with
> PTHREAD_MUTEX_RECURSIVE, which is defined in UNIX98.
That sounds good. PTHREAD_MUTEX_RECURSIVE is defined on my system.
> I will make this change and let you know when it is done.
Thank you very much.
> In the mean time, could you try to configure with --without-threads?
Done. Same result. Line 2658 of eval.c is not ifdefed, I think. So it
is always compiled in.
> With that option, guile should make no reference to pthread things.
Does not work, I think. And would not help... I'm trying 1.7.2, because
I want to use pthreads...
> --
> GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405