From: Hans Aberg <haberg@math.su.se>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: Mac OS X .dylib
Date: Sat, 30 Jan 2010 20:52:36 +0100 [thread overview]
Message-ID: <2297C01B-B713-42E4-94E1-F196A14FCA5C@math.su.se> (raw)
In-Reply-To: <87pr4rcuby.fsf@gnu.org>
On 30 Jan 2010, at 19:37, Ludovic Courtès wrote:
> The abstraction over file name extensions is handled by Libtool’s
> libltdl, used in ‘libguile/dynl.c’. Which version of Libtool/ltdl are
> you using?
I took down the latest stable before trying to compile guile:
libtool --version
ltmain.sh (GNU libtool) 2.2
> Did you try adding the directory where the ‘.dylib’ is to
> $DYLD_LIBRARY_PATH?
No, all was installed with standard './configure && make && make
install', without tweaks.
If you want me try something, please let me know.
Hans
next prev parent reply other threads:[~2010-01-30 19:52 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 [this message]
2010-01-30 18:39 ` Ken Raeburn
2010-01-30 20:03 ` Hans Aberg
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=2297C01B-B713-42E4-94E1-F196A14FCA5C@math.su.se \
--to=haberg@math.su.se \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.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).