[Xquartz-dev] libXdamage, compatibility version 3.0.0

Simone Karin Lehmann webmaster at lisanet.de
Wed Jan 7 02:38:38 PST 2009


----- original Nachricht --------

Betreff: Re: [Xquartz-dev] libXdamage, compatibility version 3.0.0
Gesendet: Mi, 07. Jan 2009
Von: Jeremy Huddleston<jeremyhu at apple.com>

> How are you building all the dependencies? Are you using fink? 
> macports? by hand?

I'm using MacPorts as a basis and have frozen most of the needed Portfiles so that I can ensure that the different builds which are provided on GIMP on OS X use the same ports versions even if they are compiled on different machines.

> 
> 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/...

yep, I know this. So let's make things more clearer.

I've build GIMP using MacPorts on 10.5.6 with XCode 3.0. So IMO this uses 10.5 SDK. 
Prior to installing XQuartz 2.3.2 libXdamage had compatibility version 2.0.0 and libgtk-x11, build with MacPorts, linked against that and everything ran well.
After upgrading my machine to XQuartz 2.3.2.1 (still 10.5.6, XCode 3.0) and rebuilding GIMP, libgtk-x11 got linked against libXdamage with compatibility version 3.0.0.
Now users complain, that GIMP doesn't launch because of an incompatible library version. This occurs if they run some XQuartz version prior to 2.3.2
So it seems to me, that XQuartz 2.3.2.1 has somehow brought this into my system.

How can this be fixed?

Does reinstalling XCode 3.0 help in any way? Or will this conflict with an installed XQuartz 2.3.2.1, if I rebuild GIMP? XCode 3.0 provides libXdamage compatibility version 2.0.0. Will this brake XQuartz 2.3.2.1 clients as they might be linked against compatibility version 3.0.0?

-skl



More information about the Xquartz-dev mailing list