[MacPorts] #30248: wine-devel: libwine.1.dylib malformed object (unknown load command 4) (was: wine-devel: ld: library not found for -lwine)

[MacPorts]

#30248: wine-devel: libwine.1.dylib malformed object (unknown load command 4)
-----------------------------------------+----------------------------------
  Reporter:  taco.nieuwenhuis@…          |       Owner:  ryandesign@…           
      Type:  defect                      |      Status:  closed                 
  Priority:  Normal                      |   Milestone:                         
 Component:  ports                       |     Version:  1.9.2                  
Resolution:  invalid                     |    Keywords:                         
      Port:  wine-devel                  |  
-----------------------------------------+----------------------------------
Changes (by ryandesign@…):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 I no longer believe this is a parallel build issue. I originally thought
 that because I saw the error "library not found for -lwine", suggesting
 something was trying to use libwine.dylib before it had been built. But on
 closer inspection I see the log says:

 {{{
 :info:build cp -p libwine.1.0.dylib libwine.1.dylib && install_name_tool
 -id @executable_path/`../../tools/relpath /opt/local/bin
 /opt/local/lib`/libwine.1.dylib libwine.1.dylib || rm -f libwine.1.dylib
 [...]
 :info:build install_name_tool: object: libwine.1.dylib malformed object
 (unknown load command 4)
 }}}

 So it did try to build libwine.dylib earlier, but install_name_tool did
 not recognize it as a valid library, so it deleted the library, causing
 the "library not found" error later.

 Googling this install_name_tool error turned up one case of a user who had
 somehow managed to replace their install_name_tool program with one from
 2002, which was far too old to understand modern Mac OS X libraries. You
 said you were able to build wine now, but your original report said Snow
 Leopard, and your new message said Lion. If, in between the failed build
 and the successful build, you upgraded to Lion, you would have had to
 upgrade Xcode right? And reinstalling Xcode would have replaced
 install_name_tool with a correct version.

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