bibledit-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [be] Installing Bibledit on Mac OS X


From: Mark Duling
Subject: Re: [be] Installing Bibledit on Mac OS X
Date: Thu, 18 Apr 2013 09:03:23 -0700

Hi Teus,

I don't know about how other port systems work, but macports installs its own libraries and apps even for things Apple puts in the base system.  For example, if you install something that uses apache it installs the latest apache from source in /opt/local and you turn off the built-in apache and use the one macports installed.  The only exceptions are for where it just isn't practical to do so.  X11 for example because compiling is difficult and Apple's just works better.  This method has pros and cons, but overall I think it is better because port authors have to deal less with multiple OS X version issues (since apple updates their libraries/apps each time) and it furthers the "sandbox" idea too.  Anyway, right or wrong that is how it works.

Yes, you're right Apple doesn't bundle gtk.  It could be a path issue as your colleague mentioned, but maybe it could also be a linking issue if bibledit links during compilation against some macports libraries and some apple ones.  I'm beyond my knowledge here, but I wonder if it would turn up anything for someone with a working bibledit 4.7 to run otool against the bibledit binary and paste the results here so we can compare the results to an installation that segfaults.

otool -L bibledit-gtk

Just a wild guess.  I see at least a few libraries in /usr/lib that are duplicated in macports.  It could turn out that there is an incompatibility with a (possibly newer) version of one of the libraries in macports.

Mark



Hi Mark,

I don't think that Mac OS X comes with its own version of Gtk installed. If
it had, why should macports install another one.

One of our colleagues thought that perhaps some program expects some
configuration file in /usr since installing from source puts the stuff
there.

I think that it is possible, by modifying the code of bibledit-gtk, to find
out what's going wrong in that routine. Perhaps it can't find the screen.
perhaps it's resizing the window to some odd values. It could be anything.
Hopefully Friday will bring more news about it.

Yes, Linux also has crash logs - useful things.

Regards, Teus


reply via email to

[Prev in Thread] Current Thread [Next in Thread]