From: Mark H Weaver <mhw@netris.org>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: 17661-done@debbugs.gnu.org
Subject: bug#17661: Some guile-2.0 asyncs functions do not link correctly
Date: Sun, 01 Jun 2014 20:55:23 -0400 [thread overview]
Message-ID: <87fvjo2kqs.fsf@yeeloong.lan> (raw)
In-Reply-To: <20140601175448.00cbf158@bother.homenet> (Chris Vine's message of "Sun, 1 Jun 2014 17:54:48 +0100")
Chris Vine <chris@cvine.freeserve.co.uk> writes:
> 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 exported, even
> though these functions are documented and appear intended to be called
> by user code.
>
> A patch, against guile-2.0.11, is below, dealing with this.
Pushed to stable-2.0, commit 12c6a47773041ff5d0a3553421d2f358d9e479a9.
Thanks!
Mark
prev parent reply other threads:[~2014-06-02 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 16:54 bug#17661: Some guile-2.0 asyncs functions do not link correctly Chris Vine
2014-06-02 0:55 ` Mark H Weaver [this message]
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=87fvjo2kqs.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=17661-done@debbugs.gnu.org \
--cc=chris@cvine.freeserve.co.uk \
/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).