unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org
Subject: Re: scm_mutex_lock and scm_mutex_unlock
Date: Sun, 23 Oct 2005 23:13:44 +0300	[thread overview]
Message-ID: <877jc4rnyf.fsf@uni-dortmund.de> (raw)
In-Reply-To: <0670f7f98de893c735f61c3d27eb60c9@lurchi.franken.de> (Michael Tuexen's message of "Sun, 23 Oct 2005 17:40:19 +0200")

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> 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.

I will make this change and let you know when it is done.

In the mean time, could you try to configure with --without-threads?
With that option, guile should make no reference to pthread things.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2005-10-23 20:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22 15:07 scm_mutex_lock and scm_mutex_unlock Michael Tuexen
2005-10-23 12:28 ` Marius Vollmer
2005-10-23 15:40   ` Michael Tuexen
2005-10-23 20:13     ` Marius Vollmer [this message]
2005-10-23 20:53       ` Michael Tuexen
2005-10-23 21:15         ` Marius Vollmer
2005-10-24 12:45           ` Michael Tuexen
2005-10-24 19:17             ` Marius Vollmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877jc4rnyf.fsf@uni-dortmund.de \
    --to=marius.vollmer@uni-dortmund.de \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).