From: Richard Shann <richard.shann@virgin.net>
To: guile-user@gnu.org
Subject: Re: statically linking in srfi modules
Date: Fri, 08 Feb 2013 09:25:53 +0000 [thread overview]
Message-ID: <1360315553.2172.132.camel@debian-box.lan> (raw)
In-Reply-To: <1360315456.2172.131.camel@debian-box.lan>
Oh - sorry, I should have mentioned, we are still on guile 1.8 (perhaps
for no good reason?), if that affects the answer.
Richard
On Fri, 2013-02-08 at 09:24 +0000, Richard Shann wrote:
> Is it possible to statically link in the srfi modules? For GNU/Denemo we
> are currently trying http://mxe.cc to build for ms windows. Guile is
> being built with --disable-shared and in consequence when denemo loads
> srfi-1 the dynamic loading it does:
> (load-extension "libguile-srfi-srfi-1-v-3" "scm_init_srfi_1")
> fails.
> If OTOH I put --enable-shared then the link fails lacking further shared
> libraries libgmp libltdl libunistring libintl libiconv.
>
> Can someone suggest how to proceed - there is no critical objection to
> using shared libraries, but all those libraries are already built in mxe
> as static libraries; is there a way to build guile with the srfi stuff
> ready linked in?
>
> Richard Shann
>
next prev parent reply other threads:[~2013-02-08 9:25 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 [this message]
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
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=1360315553.2172.132.camel@debian-box.lan \
--to=richard.shann@virgin.net \
--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).