From: Kevin Ryde <user42@zip.com.au>
To: guile-gtk@sources.redhat.com
Subject: gtk-thread.c and latest guile
Date: Sun, 06 Apr 2003 23:55:00 -0000 [thread overview]
Message-ID: <87r88f6v1v.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 255 bytes --]
The defines indicating what threading is supported have changed in the
latest cvs guile. I get some joy from the following, at least enough
to build.
* gtk-threads.c (SCM_USE_PTHREAD_THREADS, SCM_USE_COOP_THREADS):
Recognise these from latest guile.
[-- Attachment #2: gtk-threads.c.new-configs.diff --]
[-- Type: text/plain, Size: 981 bytes --]
--- gtk-threads.c.~1.4.~ 2002-12-28 07:23:25.000000000 +1000
+++ gtk-threads.c 2003-04-07 09:52:49.000000000 +1000
@@ -1,5 +1,5 @@
/* Threading for guile-gtk
- * Copyright (C) 2000, 2002 Free Software Foundation
+ * Copyright (C) 2000, 2002, 2003 Free Software Foundation
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
@@ -32,6 +32,19 @@
#include "gtk-threads.h"
+/* Guile 1.8 and up defines SCM_USE_PTHREAD_THREADS to 0 or 1, where
+ previously it was a define or not of USE_PTHREAD_THREADS. Similarly
+ SCM_USE_COOP_THREADS and USE_COOP_THREADS.
+ FIXME: It might be better to reverse the code here to use the new style,
+ and recognise the old, rather than the other way around. */
+#if SCM_USE_PTHREAD_THREADS
+#define USE_PTHREAD_THREADS
+#endif
+#if SCM_USE_COOP_THREADS
+#define USE_COOP_THREADS
+#endif
+
+
#ifdef USE_THREADS
#ifndef USE_COOP_THREADS
reply other threads:[~2003-04-06 23:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r88f6v1v.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-gtk@sources.redhat.com \
/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).