unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Richard Shann <richard.shann@virgin.net>
Cc: Andy Wingo <wingo@pobox.com>, guile-user@gnu.org
Subject: Re: statically linking in srfi modules
Date: Fri, 08 Feb 2013 16:39:38 -0500	[thread overview]
Message-ID: <874nhm7aed.fsf@tines.lan> (raw)
In-Reply-To: <1360345958.2172.181.camel@debian-box.lan> (Richard Shann's message of "Fri, 08 Feb 2013 17:52:38 +0000")

Richard Shann <richard.shann@virgin.net> writes:

> I succeeded in linking Denemo with the call 
>
> scm_c_register_extension ("libguile-srfi-srfi-1-v-3", "scm_init_srfi_1",
>                              scm_init_srfi_1, NULL);
> inserted right at the beginning of inner_main (the  value passed to
> scm_boot_guile, that is), but disappointingly I still get the error
> message when srfi-1 tries to dynamically load 
>
> <libguile-srfi-srfi-1-v-3 The specified module could not be found.>

The problem is the call to 'load-extension' near the top of
'srfi-1.scm', which again tries to load that shared library.
You'll have to remove that call from 'srfi-1.scm'.

You should probably do the same thing for libguile-srfi-srfi-13-14-v-3,
so that Denemo users who wish to use the string or character set
libraries can do so.

      Mark



  reply	other threads:[~2013-02-08 21:39 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
2013-02-08 13:21       ` Richard Shann
2013-02-08 17:52     ` Richard Shann
2013-02-08 21:39       ` Mark H Weaver [this message]
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=874nhm7aed.fsf@tines.lan \
    --to=mhw@netris.org \
    --cc=guile-user@gnu.org \
    --cc=richard.shann@virgin.net \
    --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).