Inkscape-bin crash: was "Re: Inkscape crazy slow"
~suv
suv-sf at users.sourceforge.net
Wed Sep 30 02:27:30 PDT 2009
On 30/9/09 09:38, Jeremy Huddleston wrote:
> As for your new issue...
>
>> Dyld Error Message:
>> Library not loaded: /usr/lib/libxml2.2.dylib
>> Referenced from:
>> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
>>
>> Reason: Incompatible library version: DictionaryServices requires
>> version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
>
> Well, /usr/lib/libxml2.2.dylib on my system (10.6.1) is of the correct
> version:
>
> $ otool -L /usr/lib/libxml2.2.dylib
> /usr/lib/libxml2.2.dylib:
> /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 10.3.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
> /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
> /usr/lib/libicucore.A.dylib (compatibility version 1.0.0, current version 40.0.0)
>
> where did you get your /usr/lib/libxml2.2.dylib? Did you install your
> own copy of libxml2 over the one provided by the system?
This a packaging issue with older Inkscape v0.46 binary releases:
The offending library
> libxml2.2.dylib provides version 9.0.0
is included in 'Inkscape.app/Contents/Resources/lib'.
Up to version 0.47pre1 Inkscape relied on $DYLD_LIBRARY_PATH in its
launcher script to make Inkscape.app relocatable (see bug #392693 in
Inkscape: “Conflict between bundled and system libxml dylib”:
<https://bugs.launchpad.net/inkscape/+bug/392693>).
The packaging process for recent prerelease versions rewrites the
install-names of the included dylibs, executable and shared objects to
be relative to the executable to avoid library version conflicts as
shown by above quoted Dyld error message.
hth, ~suv
More information about the macports-users
mailing list