libXdamage, compatibility version 3.0.0
Hi, I'm providing pre-build packages of GIMP on the GIMP on OS X website. With the latest build (GIMP 2.6.4) I got a lot of complaints from users about GIMP not starting. This is the error message: Dyld Error Message: Library not loaded: /usr/X11/lib/libXdamage.1.dylib Referenced from: /tmp/skl/Gimp.app/Contents/Resources/lib/libgtk- x11-2.0.0.dylib Reason: Incompatible library version: libgtk-x11-2.0.0.dylib requires version 3.0.0 or later, but libXdamage.1.dylib provides version 2.0.0 I've compiled GIMP with XQuartz 2.3.2.1, which provides the correct libXdamage version. But users who have version prior to 2.3.2 will get this error about an incompatible library. How can I avoid this problem? Which version of XQuartz do I have to install, to get libXdamage with compatibility version 2.0.0? Will a GIMP build with such an old XQuartz still run on 2.3.2.1 or later? Any other suggestions to solve this conflict? -skl
If you want your app to run on earlier versions, you need to use the 10.5 (or 10.4u) SDK. On Jan 6, 2009, at 22:49, Simone Karin Lehmann wrote:
Hi,
I'm providing pre-build packages of GIMP on the GIMP on OS X website.
With the latest build (GIMP 2.6.4) I got a lot of complaints from users about GIMP not starting. This is the error message:
Dyld Error Message: Library not loaded: /usr/X11/lib/libXdamage.1.dylib Referenced from: /tmp/skl/Gimp.app/Contents/Resources/lib/libgtk- x11-2.0.0.dylib Reason: Incompatible library version: libgtk-x11-2.0.0.dylib requires version 3.0.0 or later, but libXdamage.1.dylib provides version 2.0.0
I've compiled GIMP with XQuartz 2.3.2.1, which provides the correct libXdamage version. But users who have version prior to 2.3.2 will get this error about an incompatible library.
How can I avoid this problem? Which version of XQuartz do I have to install, to get libXdamage with compatibility version 2.0.0? Will a GIMP build with such an old XQuartz still run on 2.3.2.1 or later? Any other suggestions to solve this conflict?
-skl
Am 07.01.2009 um 08:42 schrieb Jeremy Huddleston:
If you want your app to run on earlier versions, you need to use the 10.5 (or 10.4u) SDK.
Does that mean that I have to install the XQuartz version shipped with 10.5.3 (or was it 10.5.2)? How can I do this? Will those builds still run on XQuartz 2.3.2+ ? -skl
On Jan 6, 2009, at 22:49, Simone Karin Lehmann wrote:
Hi,
I'm providing pre-build packages of GIMP on the GIMP on OS X website.
With the latest build (GIMP 2.6.4) I got a lot of complaints from users about GIMP not starting. This is the error message:
Dyld Error Message: Library not loaded: /usr/X11/lib/libXdamage.1.dylib Referenced from: /tmp/skl/Gimp.app/Contents/Resources/lib/libgtk- x11-2.0.0.dylib Reason: Incompatible library version: libgtk-x11-2.0.0.dylib requires version 3.0.0 or later, but libXdamage.1.dylib provides version 2.0.0
I've compiled GIMP with XQuartz 2.3.2.1, which provides the correct libXdamage version. But users who have version prior to 2.3.2 will get this error about an incompatible library.
How can I avoid this problem? Which version of XQuartz do I have to install, to get libXdamage with compatibility version 2.0.0? Will a GIMP build with such an old XQuartz still run on 2.3.2.1 or later? Any other suggestions to solve this conflict?
-skl
On Jan 6, 2009, at 23:48, Simone Karin Lehmann wrote:
Am 07.01.2009 um 08:42 schrieb Jeremy Huddleston:
If you want your app to run on earlier versions, you need to use the 10.5 (or 10.4u) SDK.
Does that mean that I have to install the XQuartz version shipped with 10.5.3 (or was it 10.5.2)? How can I do this? Will those builds still run on XQuartz 2.3.2+ ?
How are you building all the dependencies? Are you using fink? macports? by hand? If you build against the 10.4u SDK, it will work on 10.4, 10.5, and any version from http://xquartz.macosforge.org. If you build against 10.5 SDK, it will not work on 10.4, but will work on any version of 10.5.x and any version from http://xquartz.macosforge.org If you build against the system version installed with 10.5.x, it will not be guaranteed to work on versions of OSX less than 10.5.x (meaning if you build with 10.5.5, it won't be guaranteed to work on 10.5.4). If you build against the system version after installing an update, it will not be guaranteed to work on earlier versions of the update. This is the whole reason for providing the /Developer/SDKs/...
Jeremy Huddleston wrote: []
If you build against 10.5 SDK, it will not work on 10.4, but will work on any version of 10.5.x and any version from http://xquartz.macosforge.org
At least, that's the theory. A quick look seems to tell me that it is not true: libXdamage has compatibility_version 2.0.0 only in the MacOSX10.5.sdk that comes with Xcode-3.0; starting from Xcode-3.1, it switched to compatibility_version 3.0.0. This means that you need to get Xcode-3.0 in order for this to work on any version of 10.5.x. And, BTW, the MacOSX10.4u.sdk does not contain any version of libXdamage. -- Martin
participants (3)
-
Jeremy Huddleston
-
Martin Costabel
-
Simone Karin Lehmann