unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Richard Shann <richard.shann@virgin.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org
Subject: Re: statically linking in srfi modules
Date: Fri, 08 Feb 2013 13:02:01 +0000	[thread overview]
Message-ID: <1360328521.2172.146.camel@debian-box.lan> (raw)
In-Reply-To: <87sj5711wu.fsf@pobox.com>

Hmm, I can't find scm_c_register_extension in the guile reference index,
and though including libguile.h finds the function I get the error
message scm_init_srfi_1 undeclared... 
Hunting around for this symbol I see the header srfi-1.h with it
declared but
#include "guile/srfi/srfi-1.h"
gives a heap of errors...

It looks like this module is the only one doing the dynamic loading
thing, judging by grepping for extension in the files, but is there a
way of knowing?

Thanks in advance,

Richard



On Fri, 2013-02-08 at 12:27 +0100, Andy Wingo wrote:
> On Fri 08 Feb 2013 10:25, Richard Shann <richard.shann@virgin.net> writes:
> 
> > On Fri, 2013-02-08 at 09:24 +0000, Richard Shann wrote:
> >> Is it possible to statically link in the srfi modules?
> >> (load-extension "libguile-srfi-srfi-1-v-3" "scm_init_srfi_1")
> >> fails.
> 
> You can link it in I think, but then you will need to call
> 
>   scm_c_register_extension ("libguile-srfi-srfi-1-v-3", "scm_init_srfi_1",
>                              scm_init_srfi_1, NULL)
> 
> somewhere in your C code.
> 
> > Oh - sorry, I should have mentioned, we are still on guile 1.8 (perhaps
> > for no good reason?), if that affects the answer.
> 
> Same answer.  Guile 2.0 is much faster if that matters to you :)
> 
> Andy





  reply	other threads:[~2013-02-08 13:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08  9:24 statically linking in srfi modules Richard Shann
2013-02-08  9:25 ` Richard Shann
2013-02-08 11:27   ` Andy Wingo
2013-02-08 13:02     ` Richard Shann [this message]
2013-02-08 13:21       ` Richard Shann
2013-02-08 17:52     ` Richard Shann
2013-02-08 21:39       ` Mark H Weaver
2013-02-08 22:11         ` Mark H Weaver
2013-02-08 22:36           ` Richard Shann
2013-02-09 12:13           ` Richard Shann
2013-02-09 15:10             ` Mark H Weaver
2013-02-09 15:32               ` Mark H Weaver
2013-02-09 17:57                 ` Richard Shann
2013-02-10  2:00                   ` Mark H Weaver
2013-02-10 11:11                     ` Richard Shann
2013-02-10 15:35                       ` Mark H Weaver
2013-02-10 17:24                         ` Richard Shann
2013-02-11  2:02                           ` Mark H Weaver
2013-02-11 10:05                             ` Richard Shann
2013-02-11 13:07                               ` Richard Shann
2013-02-11 17:03                                 ` Mark H Weaver
2013-02-12 12:58                                   ` Richard Shann
2013-02-12 19:01                                     ` Mark H Weaver
2013-02-12 21:38                                       ` Ludovic Courtès
2013-02-09 18:52                 ` Richard Shann
2013-02-08 23:44         ` Ludovic Courtès

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=1360328521.2172.146.camel@debian-box.lan \
    --to=richard.shann@virgin.net \
    --cc=guile-user@gnu.org \
    --cc=wingo@pobox.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).