From: Greg Troxel <gdt@ir.bbn.com>
To: "Neil Jerram" <neiljerram@googlemail.com>
Cc: guile-devel@gnu.org
Subject: Re: is guile thought to work on Mac OS X???
Date: Mon, 12 Jan 2009 10:06:51 -0500 [thread overview]
Message-ID: <rmihc44va0k.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <49dd78620901101447m4de1fb44n2234f285eb75c8bc@mail.gmail.com> (Neil Jerram's message of "Sat, 10 Jan 2009 22:47:22 +0000")
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
"Neil Jerram" <neiljerram@googlemail.com> writes:
> 2009/1/10 Greg Troxel <gdt@ir.bbn.com>:
>
>> is load-extension expected to deal with this, and perhaps the problem
>> is a stray .so in a call that shouldn't be there?
>
> I would guess that it is libltdl's job to know that the correct suffix
> on MacOS is .dylib.
This seems to be a ltdl issue. When I run dtruss, I find an attempt to
open the .so followed by failure.
On my system there is a .la which correctly lists the .dylib.
[-- Attachment #2: Type: application/pgp-signature, Size: 193 bytes --]
next prev parent reply other threads:[~2009-01-12 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 20:28 is guile thought to work on Mac OS X??? Greg Troxel
2009-01-10 22:47 ` Neil Jerram
2009-01-12 15:06 ` Greg Troxel [this message]
2009-01-14 21:54 ` Neil Jerram
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=rmihc44va0k.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=neiljerram@googlemail.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).