From: Hans Aberg <haberg@math.su.se>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: bug-guile@gnu.org
Subject: Re: Mac OS X .dylib
Date: Sat, 30 Jan 2010 21:03:31 +0100 [thread overview]
Message-ID: <B344FF57-4393-4FD5-9BF9-8D4FE0C43DD3@math.su.se> (raw)
In-Reply-To: <B35252FC-EEB1-414C-A0C9-9B983335E065@raeburn.org>
On 30 Jan 2010, at 19:39, Ken Raeburn wrote:
> The Mac OS X situation is a bit more complicated than on "normal"
> ELF-based UNIX systems; shared libraries and dynamically loadable
> objects are not the same thing. It's easy to assume they're
> equivalent when working mostly on ELF or Windows systems where .so
> or .dll files work for both, but it's not always true. GNU libtool
> even has options for creating loadable modules as distinct from
> regular shared libraries.
Sure, it would be best to only load .dylib, but I suspect that there
might be .dylib libraries with the .so extension on Mac OS X, due to
past practice. Then such programs will suddenly break. One program
using Guile is LilyPond, and I have a vague memory of they mentioning
the .so problem on Mac OS X, but I do not recall details.
If .dylib fails and it tries .so which isn't on the .dylib format,
then the function should give an error. So it is harmless.
Hans
next prev parent reply other threads:[~2010-01-30 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 14:41 Mac OS X .dylib Hans Aberg
2010-01-30 18:37 ` Ludovic Courtès
2010-01-30 19:52 ` Hans Aberg
2010-01-30 18:39 ` Ken Raeburn
2010-01-30 20:03 ` Hans Aberg [this message]
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=B344FF57-4393-4FD5-9BF9-8D4FE0C43DD3@math.su.se \
--to=haberg@math.su.se \
--cc=bug-guile@gnu.org \
--cc=raeburn@raeburn.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).