[MacPorts] #27744: wxWidgets-devel lib has incorrect install name

[MacPorts]

#27744: wxWidgets-devel lib has incorrect install name
-----------------------------------------+----------------------------------
 Reporter:  singingwolfboy@…             |       Owner:  jwa@…           
     Type:  defect                       |      Status:  new             
 Priority:  Normal                       |   Milestone:                  
Component:  ports                        |     Version:  1.9.2           
 Keywords:                               |        Port:  wxWidgets-devel 
-----------------------------------------+----------------------------------
 I'm developing a new port that relies on a lib installed by wxWidgets-
 devel, and I'm getting this error when I try to run it:

 {{{
 dbaumgold:src baumgold$ ./bitcoin
 dyld: Library not loaded:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
 .org_release_ports_graphics_wxWidgets-
 devel/work/wxWidgets-2.9.1/build/lib/libwx_osx_cocoau-2.9.1.0.0.dylib
   Referenced from:
 /opt/local/var/macports/build/_Users_baumgold_Dropbox_ports_crypto_bitcoin/work/bitcoin-0.3.19/src/./bitcoin
   Reason: image not found
 Trace/BPT trap
 }}}

 A quick google search revealed that this seems to be the fault of the
 wxWidgets-devel port. (http://lists.apple.com/archives/xcode-
 users/2009/aug/msg00165.html) Apparently, dynamic libraries have an
 "install name" that is used when dynamically linking from other software.
 libwx_osx_cocoau-2.9.1.0.0.dylib has an incorrect install name, at least
 on my system:

 {{{
 dbaumgold:bitcoin-0.3.19 baumgold$ otool -D /opt/local/lib/wx-
 devel/libwx_osx_cocoau-2.9.1.0.0.dylib
 /opt/local/lib/wx-devel/libwx_osx_cocoau-2.9.1.0.0.dylib:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
 .org_release_ports_graphics_wxWidgets-
 devel/work/wxWidgets-2.9.1/build/lib/libwx_osx_cocoau-2.9.1.0.0.dylib
 }}}

 This should be fixed so that other applications can build and run against
 this library. Other libraries in this port may have the same issue, but I
 haven't tested.

 For reference, I'm running 10.6.5 on an Intel Macbook Pro.

-- 
Ticket URL: <https://trac.macports.org/ticket/27744>
MacPorts <http://www.macports.org/>
Ports system for Mac OS