From: Hans Aberg <haberg@math.su.se>
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Cc: bug-guile@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Ken Raeburn" <raeburn@raeburn.org>,
bug-libtool@gnu.org
Subject: Re: Mac OS X .dylib not working
Date: Tue, 2 Feb 2010 18:15:22 +0100 [thread overview]
Message-ID: <51A25259-AD5F-4D39-9319-C173F424568F@math.su.se> (raw)
In-Reply-To: <alpine.GSO.2.01.1002021046230.17824@freddy.simplesystems.org>
On 2 Feb 2010, at 17:52, Bob Friesenhahn wrote:
> Unless I am missing something, the question to be answered is if
> Guile requests opening modules using a name like
> "module.so" (assuming a particular naming scheme),
> "module.la" (using libltdl as originally intended), or bare
> "module" (using libltdl heuristics, which tries several
> incantations, such as looking for .la, and .so).
On the Bug-Guile list, Ludovic Courtès said it was the last one ,
specifically the code in 'ibguile/dynl.c', which looks like:
static void *
sysdep_dynl_link (const char *fname, const char *subr)
{
lt_dlhandle handle;
handle = lt_dlopenext (fname);
if (NULL == handle)
{
SCM fn;
SCM msg;
fn = scm_from_locale_string (fname);
msg = scm_from_locale_string (lt_dlerror ());
scm_misc_error (subr, "file: ~S, message: ~S", scm_list_2 (fn,
msg));
}
return (void *) handle;
}
> OS-X's module loading does not care about the file extension.
So from what you say, the problem may simply be that .dylib isn't in
the list.
Hans
next prev parent reply other threads:[~2010-02-02 17:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 14:26 Mac OS X .dylib not working 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-03-03 19:32 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
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
2011-03-03 19:53 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=51A25259-AD5F-4D39-9319-C173F424568F@math.su.se \
--to=haberg@math.su.se \
--cc=bfriesen@simple.dallas.tx.us \
--cc=bug-guile@gnu.org \
--cc=bug-libtool@gnu.org \
--cc=ludo@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).