From: Hans Aberg <haberg@math.su.se>
To: bug-guile@gnu.org
Subject: Mac OS X .dylib
Date: Sat, 30 Jan 2010 15:41:03 +0100 [thread overview]
Message-ID: <DE114180-13F6-498C-9E48-9407E5CFBBA7@math.su.se> (raw)
[I'm not on this list, so please cc me.]
It seems guile-1.8.7 does not admit dynamic library file name
extensions .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4),
despite the manual saying guile should adapt to local standards. The
example in the manual sec. 4.2.1 works fine with
gcc -dynamiclib -lguile -o libguile-bessel.so bessel.c
but not if changed to libguile-bessel.dylib, giving the error within
guile:
standard input:2:1: file: "libguile-bessel", message: "file not
found"
On Mac OS X, it should probably look for .dylib first, and perhaps .so
for backwards compatibility.
Hans
next reply other threads:[~2010-01-30 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 14:41 Hans Aberg [this message]
2010-01-30 18:37 ` Mac OS X .dylib Ludovic Courtès
2010-01-30 19:52 ` Hans Aberg
2010-01-30 18:39 ` Ken Raeburn
2010-01-30 20:03 ` Hans Aberg
2010-01-30 19:30 ` Andy Wingo
2010-01-30 22:10 ` Hans Aberg
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=DE114180-13F6-498C-9E48-9407E5CFBBA7@math.su.se \
--to=haberg@math.su.se \
--cc=bug-guile@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).