unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Michael Ellis <michael.f.ellis@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: FFI on OS X?
Date: Thu, 03 Mar 2011 20:49:34 +0100	[thread overview]
Message-ID: <m3ei6ogf1t.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTin9UrztOHYw3AYu9187mWEoJY-=bVyY7gdTp1+5@mail.gmail.com> (Michael Ellis's message of "Thu, 3 Mar 2011 11:53:31 -0500")

On Thu 03 Mar 2011 17:53, Michael Ellis <michael.f.ellis@gmail.com> writes:

> On Thu, Mar 3, 2011 at 9:36 AM, Andreas Rottmann <a.rottmann@gmx.at> wrote:
>> Hans Aberg <haberg-1@telia.com> writes:
>
>>>> Why does this fail? �Can you strace it?
>>>
>>> If you tell me how. :-)
>>>
>> Apparently, on OS X, "dtruss" does fulfill the role of "strace":
>> <http://humberto.digi.com.br/blog/2008/02/25/strace-on-mac-os-x-leopard/>.
>
> For the record, here's some dtruss output  created when I try to
> dynamic-link a library that doesn't have a .so softlink, ie
> (dynamic-link "libf77lapack")

Aaahh yes I remember now.  It should have been looking for .dylib but
only wanted .so links, right?  I think this is a libltdl bug.

    http://thread.gmane.org/gmane.lisp.guile.bugs/4483

There were a number of issues there, but I think the point about .dylib
getting added to the default suffix list on OS X got lost.

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2011-03-03 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 20:07 FFI on OS X? Michael Ellis
2011-03-02 20:23 ` Hans Aberg
2011-03-02 21:22 ` Andy Wingo
2011-03-02 22:15   ` Hans Aberg
2011-03-03  9:25     ` Andy Wingo
2011-03-03  9:48       ` Hans Aberg
2011-03-03 14:36         ` Andreas Rottmann
2011-03-03 16:53           ` Michael Ellis
2011-03-03 19:49             ` Andy Wingo [this message]

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=m3ei6ogf1t.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=michael.f.ellis@gmail.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).