[MacPorts] #29611: port install wine: upgrade pkgconfig failed

[MacPorts]

#29611: port install wine: upgrade pkgconfig failed
-------------------------------+--------------------------------------------
 Reporter:  eklypse@…          |       Owner:  ryandesign@…           
     Type:  defect             |      Status:  new                    
 Priority:  Normal             |   Milestone:                         
Component:  ports              |     Version:  1.9.2                  
 Keywords:                     |        Port:  pkgconfig wine         
-------------------------------+--------------------------------------------

Comment(by ryandesign@…):

 There are multiple ports involved, but there appears to be a common cause.

 When configuring pkgconfig, it ran into problems running gsed:

 {{{
 checking for a sed that does not truncate output... ./configure: line
 3952: 86407 Trace/BPT trap          "$ac_path_SED" -f conftest.sed <
 "conftest.nl" > "conftest.out" 2> /dev/null
 }}}

 It doesn't say why, but then it has problems running gawk because libintl
 (from the gettext port) was not the right architecture, and we can assume
 that's also the reason gsed couldn't run, as it also depends on gettext.

 {{{
 dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/gawk
   Reason: no suitable image found.  Did find:
         /opt/local/lib/libintl.8.dylib: mach-o, but wrong architecture
 }}}

 When running wine, it cannot use libz (from the zlib port) because it is
 not the right architecture:

 {{{
 dyld: Library not loaded: /opt/local/lib/libz.1.dylib
   Referenced from: /opt/local/libexec/wine/wine
   Reason: no suitable image found.  Did find:
         /opt/local/lib/libz.1.dylib: mach-o, but wrong architecture
 }}}

 All of this suggests that some of your MacPorts libraries have been
 replaced with ones that are not the right architecture. One way this can
 happen is if you install third-party software, not using MacPorts, whose
 installer was itself built using MacPorts configured for its default
 prefix, and built for a different architecture than the one you're now
 using. Read [wiki:ProblemHotlist#xmlwf] for more on this problem, and the
 solution, which is unfortunately to uninstall MacPorts and all ports and
 start over, and do not install such third-party software outside of
 MacPorts in the future, if it is available in MacPorts.

 Another reason for architecture mismatches is if you upgrade Mac OS X
 (typically, upgrade from Leopard or earlier to Snow Leopard or later) or
 switch to a new Mac (from a PowerPC Mac to an Intel Mac, or from a 32-bit
 Intel Mac to a 64-bit Intel Mac) and use Migration Assistant to migrate
 your data (including MacPorts) to the new machine. This is discussed
 further in [wiki:Migration] along with an automated port reinstallation
 script you might find helpful.

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