unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Hans Aberg <haberg@math.su.se>
To: Peter O'Gorman <peter@pogma.com>
Cc: bug-guile@gnu.org, Ken Raeburn <raeburn@raeburn.org>,
	bug-libtool@gnu.org
Subject: Re: Mac OS X .dylib not working
Date: Thu, 4 Feb 2010 17:58:27 +0100	[thread overview]
Message-ID: <DDBCEEDD-4441-49DA-8599-23F79E5A2B38@math.su.se> (raw)
In-Reply-To: <20100204153444.GC23972@tw.local>

On 4 Feb 2010, at 16:34, Peter O'Gorman wrote:

>> ----
>> $ lilypond empty.ly
>> dyld: loaded: /Applications/LilyPond.app/Contents/Resources/bin/../
>> lib//libintl.8.dylib
>> dyld: loaded: /Applications/LilyPond.app/Contents/Resources/bin/../
>> lib//libguile.17.dylib
>> dyld: loaded: /Applications/LilyPond.app/Contents/Resources/bin/../
>> lib//libltdl.7.dylib
>> GNU LilyPond 2.13.7
>> dyld: loaded: /usr/local/lib/libguile-srfi-srfi-1-v-3.3.dylib
>> dyld: loaded: /usr/local/lib/libguile.17.dylib
>> dyld: loaded: /usr/local/lib/libintl.8.dylib
>> dyld: loaded: /usr/local/lib/libgmp.3.dylib
>> dyld: loaded: /usr/local/lib/libltdl.7.dylib
>> Segmentation fault
>
> So lilypond starts up fine, but guile's first dlopen() for
> libguile-srfi-srfi-1-v-3.3 causes the library in /usr/local/lib to be
> loaded (and its dependent libraries, including another libguile,
> libintl, and libltdl). Ensuring that the search path is correct would
> fix this problem, look at setting the LTDL_LIBRARY_PATH environment
> variable, perhaps?

Sorry, I should have answered this one: the variable isn't set, and  
exporting it to say
   LTDL_LIBRARY_PATH=/Applications/LilyPond.app/Contents/Resources/lib
before starting 'lilypond' does not change the behavior.

   Hans

  parent reply	other threads:[~2010-02-04 16:58 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
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 [this message]
  -- 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=DDBCEEDD-4441-49DA-8599-23F79E5A2B38@math.su.se \
    --to=haberg@math.su.se \
    --cc=bug-guile@gnu.org \
    --cc=bug-libtool@gnu.org \
    --cc=peter@pogma.com \
    --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).