From: Chris Vine <chris@cvine.freeserve.co.uk>
To: guile-devel <guile-devel@gnu.org>
Subject: async blocking function linking
Date: Sun, 4 May 2014 11:34:19 +0100 [thread overview]
Message-ID: <20140504113419.0c13fb07@laptop.homenet> (raw)
Hi,
guile-2.0's scm_c_call_with_blocked_asyncs,
scm_c_call_with_unblocked_asyncs, scm_dynwind_block_asyncs and
scm_dynwind_unblock_asyncs will not link for me using 32-bit
ubuntu-14.04 (gcc-4.8.2/guile-2.0.9) or 32-bit slackware-14.1
(gcc-4.9.0/guile-2.0.11). I do not have a machine to test a 64-bit
system at present.
The issue appears to be that this part of the API is not marked as
exported, even though these functions are documented and presumably
intended to be called by user code.
A trivial patch, against guile-2.0.11, is attached dealing with this.
Chris
--- guile-2.0.11/libguile/async.h.orig 2014-05-04 10:38:14.631777784 +0100
+++ guile-2.0.11/libguile/async.h 2014-05-04 10:45:45.615763664 +0100
@@ -44,10 +44,10 @@
SCM_API SCM scm_noop (SCM args);
SCM_API SCM scm_call_with_blocked_asyncs (SCM proc);
SCM_API SCM scm_call_with_unblocked_asyncs (SCM proc);
-void *scm_c_call_with_blocked_asyncs (void *(*p) (void *d), void *d);
-void *scm_c_call_with_unblocked_asyncs (void *(*p) (void *d), void *d);
-void scm_dynwind_block_asyncs (void);
-void scm_dynwind_unblock_asyncs (void);
+SCM_API void *scm_c_call_with_blocked_asyncs (void *(*p) (void *d), void *d);
+SCM_API void *scm_c_call_with_unblocked_asyncs (void *(*p) (void *d), void *d);
+SCM_API void scm_dynwind_block_asyncs (void);
+SCM_API void scm_dynwind_unblock_asyncs (void);
/* Critical sections */
next reply other threads:[~2014-05-04 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 10:34 Chris Vine [this message]
2014-06-02 0:54 ` async blocking function linking Mark H Weaver
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=20140504113419.0c13fb07@laptop.homenet \
--to=chris@cvine.freeserve.co.uk \
--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).