From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: guile-devel@gnu.org
Subject: Re: scm_mutex_lock and scm_mutex_unlock
Date: Sun, 23 Oct 2005 17:40:19 +0200 [thread overview]
Message-ID: <0670f7f98de893c735f61c3d27eb60c9@lurchi.franken.de> (raw)
In-Reply-To: <87fyqss9h1.fsf@uni-dortmund.de>
Hi Marius,
thanks, that works. It now stops at
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.
Best regards
Michael
On Oct 23, 2005, at 14:28 Uhr, Marius Vollmer wrote:
> Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
>
>> I'm trying to compile guile-1.7.2 on Mac OS X 10.3.9. The compilation
>> breaks because scm_mutex_lock and scm_mutex_unlock are used in
>> libguile/arbiters.c but the compiler and I can not find a definition
>> of those functions. Where are they defined?
>
> That's a bug in guile 1.7.2 that has been fixed in CVS:
>
> 2005-03-18 Kevin Ryde <user42@zip.com.au>
>
> * arbiters.c (FETCH_STORE) [generic C]: Should be
> scm_i_scm_pthread_mutex_lock/unlock now. Reported by Ludovic Courtès.
>
> You could try a recent 'unstable' snapshot:
>
> ftp://ftp.dt.e-technik.uni-dortmund.de/pub/guile/snapshots/guile-
> core.unstable.tar.gz
>
>
> --
> 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
next prev parent reply other threads:[~2005-10-23 15:40 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 [this message]
2005-10-23 20:13 ` Marius Vollmer
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=0670f7f98de893c735f61c3d27eb60c9@lurchi.franken.de \
--to=michael.tuexen@lurchi.franken.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).