[MacPorts] #17356: gtk2 fails to link with libXdamage.1.1.0.dylib

[MacPorts]

#17356: gtk2 fails to link with libXdamage.1.1.0.dylib
------------------------------------+---------------------------------------
  Reporter:  golekipro@…            |       Owner:  macports-tickets@…                   
      Type:  defect                 |      Status:  reopened                             
  Priority:  Normal                 |   Milestone:  Port Bugs                            
 Component:  ports                  |     Version:  1.6.0                                
Resolution:                         |    Keywords:  easytag easytag-devel                
      Port:  gtk2                   |  
------------------------------------+---------------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@…, jeremyhu@… (added)
  * status:  closed => reopened
  * resolution:  duplicate =>


Comment:

 This ticket was marked as a duplicate of #14592 but that is a problem with
 a different library, libXrandr. The file ${x11prefix}/lib/libXrandr.la
 used to refer to the symlink libXrandr.2.0.0.dylib but that does not exist
 on clean installs of the current version of Leopard. According to #17008
 and [LeopardProblems#usrX11liblibXrandr.2.0.0.dylib:Nosuchfileordirectory
 LeopardProblems], upgrading to Xcode 3.1 fixes the .la file to correctly
 refer to libXrandr.2.1.0.dylib instead which does exist, so the problem
 for that library is resolved.

 However the same is not true of libXdamage.1.1.0.dylib, the file of issue
 in this ticket. Even on Mac OS X 10.5.6 with Xcode 3.1.2, the file
 ${x11prefix}/lib/libXdamage.la refers to the library
 libXdamage.1.1.0.dylib which does not exist. The symlink
 libXdamage.1.0.0.dylib does exist. I did not try installing XQuartz as
 suggested above because I do not agree that it is a correct solution to
 force users to install that.

 We do have a port xorg-libXdamage in MacPorts now. I do not know if that
 would perhaps be part of an appropriate fix. Or, if as
 [comment:ticket:17008:6 Jeremy said in #17008], the true bug is that the
 system's .la file refers to the wrong library version, then the port
 should check for this and explain to the user how to fix the libXdamage.la
 file if necessary.

-- 
Ticket URL: <http://trac.macports.org/ticket/17356#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS