From: Chris Vine <chris@cvine.freeserve.co.uk>
To: guile-user@gnu.org
Subject: Re: scm_dynwind_block_asyncs() and scm_dynwind_unblock_asyncs() won't link
Date: Sun, 4 May 2014 11:35:53 +0100 [thread overview]
Message-ID: <20140504113553.7c4d03d8@laptop.homenet> (raw)
In-Reply-To: <20140503205056.2557a452@laptop.homenet>
On Sat, 3 May 2014 20:50:56 +0100
Chris Vine <chris@cvine.freeserve.co.uk> wrote:
> Hi,
>
> I am having a linking problem with scm_dynwind_block_asyncs() and
> scm_dynwind_unblock_asyncs() with guile-2.0.11, but only with those
> two functions. This can be reduced to the following test case:
>
> #include <libguile.h>
>
> int main(void)
> {
> scm_dynwind_block_asyncs();
> scm_dynwind_unblock_asyncs();
> return 0;
> }
>
> when compiled with:
>
> gcc -o guile-test `pkg-config guile-2.0 --cflags --libs`
> guile-test.c
>
> they fail to link for me, emitting:
>
> /tmp/cc3wakQm.o: In function `main':
> guile-test.c:(.text+0x12): undefined reference to
> `scm_dynwind_block_asyncs' guile-test.c:(.text+0x17): undefined
> reference to `scm_dynwind_unblock_asyncs' collect2: error: ld
> returned 1 exit status
>
> However, all other guile functions appear to link correctly, and
>
> nm -Ca /usr/lib/libguile-2.0.so | grep scm_dynwind.*asyncs
>
> shows the two functions are in the shared library file. I am at a
> complete loss. Can someone test their own installations of
> guile-2.0.11 and/or tell me what I might be doing wrong?
If anyone is reading this on the archive, the problem is that
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 are not explicitly marked as exported in
async.h. I have sent a trivial patch to the guile-devel mailing list.
Chris
prev parent reply other threads:[~2014-05-04 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 19:50 scm_dynwind_block_asyncs() and scm_dynwind_unblock_asyncs() won't link Chris Vine
2014-05-04 10:35 ` Chris Vine [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=20140504113553.7c4d03d8@laptop.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=guile-user@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).