From: Andy Wingo <wingo@pobox.com>
To: dev.admin@ntlworld.com
Cc: guile-user@gnu.org
Subject: Re: [darwin] building shared libraries (.so) instead of dynamic libraries.
Date: Fri, 01 Oct 2010 16:21:39 +0200 [thread overview]
Message-ID: <m3zkuyj8ng.fsf@unquote.localdomain> (raw)
In-Reply-To: <DA76BE17-4F74-43B5-947E-E85F5600DED4@ntlworld.com> (dev admin's message of "Fri, 1 Oct 2010 14:19:52 +0100")
On Fri 01 Oct 2010 15:19, dev.admin@ntlworld.com writes:
> ERROR: In procedure dynamic-link:
> ERROR: file: "libguile-srfi-srfi-1-v-3", message: "dlopen(libguile-
> srfi-srfi-1-v-3.so, 9): image not found"
Which version of Guile? Where did you install Guile?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-10-01 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 13:19 [darwin] building shared libraries (.so) instead of dynamic libraries dev.admin
2010-10-01 14:21 ` Andy Wingo [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-01 14:24 dev.admin
2010-10-03 10:29 ` Andy Wingo
2010-10-03 16:06 ` Hans Aberg
2010-12-04 14:10 ` dev.admin
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=m3zkuyj8ng.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=dev.admin@ntlworld.com \
--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).