[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                   |  
------------------------------------+---------------------------------------

Comment(by ryandesign@…):

 Not quite... I have:

 {{{
 $ ls -l /usr/X11/lib/libXdamage*
 lrwxr-xr-x  1 root  wheel     18 Jul  3 15:49
 /usr/X11/lib/libXdamage.1.0.0.dylib -> libXdamage.1.dylib
 -rwxr-xr-x  1 root  wheel  88448 Jul 31 20:57
 /usr/X11/lib/libXdamage.1.dylib
 lrwxr-xr-x  1 root  wheel     18 Jul  3 15:49
 /usr/X11/lib/libXdamage.dylib -> libXdamage.1.dylib
 -rwxr-xr-x  1 root  wheel    936 May 10  2008 /usr/X11/lib/libXdamage.la
 }}}

 But:

 {{{
 $ grep dylib /usr/X11/lib/libXdamage.la
 dlname='libXdamage.1.dylib'
 library_names='libXdamage.1.dylib libXdamage.dylib libXdamage.1.1.0.dylib'
 }}}

 So it's not dlname but library_names that's wrong. But as you say we could
 perhaps reinplace that file to fix it. Then again, so could an Apple
 update (be it a Mac OS X update or an Xcode update).

 Then again, if it references the wrong library name, and clearly gtk2
 fails to compile as a result, how could any other port have successfully
 compiled against that library? And if there is thus no MacPorts library
 linking with that .la, we could again delete it, if that is the generally
 agreed-upon fix.

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