From: Hans Aberg <haberg-1@telia.com>
To: Peter O'Gorman <peter@pogma.com>
Cc: "Guile bug" <bug-guile@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>,
bug-libtool@gnu.org
Subject: Re: Mac OS X .dylib not working
Date: Fri, 4 Mar 2011 10:44:54 +0100 [thread overview]
Message-ID: <24B671DD-89B7-4FBC-BDC5-39E6C058872E@telia.com> (raw)
In-Reply-To: <4D705581.1030701@pogma.com>
On 4 Mar 2011, at 03:59, Peter O'Gorman wrote:
>>> Mac OS X does not care about file name extensions; .dylib is just a convention for native dynamic libraries.
>
> The static linker when it sees a -l flag will look for files beginning with "lib" and ending in ".dylib", ".so" (though this is recent and perhaps not documented) and ".a". So, I think you could say that it cares about file name extensions.
One is free to implement programs that do such things.
>>> So the wanted behavior is to first try opening a library without adding an extension, and then try out different endings. On Mac OS X, it would be best trying out .dylib first - I haven't seen any other ending in use.
>
> It does seem as though guile should sometimes be trying lt_dlopen() first - then libltdl will attempt to open whatever it's given.
That might be an hack.
>> -- the libtool archive extension .la
>> -- the extension used for native dynamically loadable modules on the
>> host platform, e.g., .so, .sl, etc.
>
> On Mac OS X, libtool's idea of the native dynamically loadable module extension is ".so", and it's not going to change.
>
> However, I can see the point that libltdl should try .dylib as well as .so for lt_dlopenext on Mac OS X. I will come up with a patch for that.
The important thing is to try .dylib - all libraries I have sen use it. It can of course try .so as well.
Hans
next prev parent reply other threads:[~2011-03-04 9:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 19:32 Mac OS X .dylib not working Hans Åberg
2011-03-03 19:56 ` Michael Ellis
2011-03-04 2:59 ` Peter O'Gorman
2011-03-04 3:41 ` Michael Ellis
2011-03-04 8:59 ` Andy Wingo
2011-03-04 9:44 ` Hans Aberg [this message]
2011-03-04 18:07 ` Peter O'Gorman
2011-03-04 18:47 ` Ralf Wildenhues
2011-03-04 19:00 ` Peter O'Gorman
2011-03-05 16:16 ` Peter O'Gorman
2011-03-04 3:00 ` Bob Friesenhahn
2011-03-04 3:48 ` Michael Ellis
2011-03-04 17:04 ` Ralf Wildenhues
2011-03-04 9:47 ` Hans Aberg
-- strict thread matches above, loose matches on Subject: below --
2011-03-03 19:53 Hans Aberg
2010-02-01 14:26 Hans Aberg
2010-02-02 6:42 ` Ralf Wildenhues
2010-02-02 9:08 ` Hans Aberg
2010-02-02 14:20 ` Ken Raeburn
2010-02-02 15:48 ` Hans Aberg
2010-02-02 16:52 ` Bob Friesenhahn
2010-02-02 17:15 ` Hans Aberg
2010-02-02 18:01 ` Ludovic Courtès
2010-02-03 14:23 ` Ken Raeburn
2010-02-03 15:10 ` Ludovic Courtès
2010-02-04 12:40 ` Hans Aberg
2010-02-04 13:49 ` Peter O'Gorman
2010-02-04 15:21 ` Hans Aberg
2010-02-04 15:34 ` Peter O'Gorman
2010-02-04 16:52 ` Hans Aberg
2010-02-04 16:58 ` 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=24B671DD-89B7-4FBC-BDC5-39E6C058872E@telia.com \
--to=haberg-1@telia.com \
--cc=bug-guile@gnu.org \
--cc=bug-libtool@gnu.org \
--cc=ludo@gnu.org \
--cc=peter@pogma.com \
/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).