From: ludo@gnu.org (Ludovic Courtès)
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: Guile Build Errors
Date: Mon, 05 Oct 2009 11:02:01 +0200 [thread overview]
Message-ID: <87my46tdrq.fsf@gnu.org> (raw)
In-Reply-To: <87zl86iyoe.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sun, 04 Oct 2009 23:25:53 +0100")
Hi,
Neil Jerram <neil@ossau.uklinux.net> writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Note that you can already use (or rather debug ;-)) Guile without
>> `dlpreopen'. You just won't be able to load modules that call
>> `load-extension'. In 1.8, it means you cannot use SRFI-1 and SRFI-60.
>
> What about statically linking all of the necessary libraries, and adding
> a scm_c_register_extension () call to the application startup code for
> each (load-extension ...) call that you expect Scheme code to make?
> Wouldn't that work?
Yes, that should work, but it’s a bit of kludge in the sense that the
application shouldn’t have to know about all this.
Thanks,
Ludo’.
prev parent reply other threads:[~2009-10-05 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 8:19 Guile Build Errors bornlibra23
2009-08-31 12:38 ` Ludovic Courtès
2009-09-01 8:30 ` bornlibra23
2009-09-02 8:44 ` Ludovic Courtès
2009-09-02 9:29 ` bornlibra23
2009-09-02 11:49 ` Ludovic Courtès
2009-10-04 22:25 ` Neil Jerram
2009-10-05 9:02 ` Ludovic Courtès [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=87my46tdrq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).