[MacPorts] #42884: serf1 build failed: install_name_tool: malformed object (unknown load command 4)

MacPorts noreply at macports.org
Mon Mar 17 03:11:49 PDT 2014


#42884: serf1 build failed: install_name_tool: malformed object (unknown load
command 4)
-----------------------------+--------------------------------
  Reporter:  macports.org@…  |      Owner:  macports-tickets@…
      Type:  defect          |     Status:  closed
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.2.1
Resolution:  invalid         |   Keywords:
      Port:  serf1           |
-----------------------------+--------------------------------

Comment (by ryandesign@…):

 Replying to [comment:2 macports.org@…]:
 > Wouldn't it help to decrease the number of invalid tickets, if the port
 system would check the binaries as configure-scripts do that?

 What, specifically, are you suggesting we have MacPorts do in this case?
 Check, every time MacPorts runs, that install_name_tool is the correct
 version for the current version of OS X? That would require at minimum
 that we be able to determine the current version of install_name_tool, and
 then maintain a list of acceptable version numbers for each version of OS
 X. And as far as I can tell, the install_name_tool command does not accept
 a `--version` or `-v` argument so I don't know how to determine its
 version. Anyway, the command line tools comprises thousands of files; we
 couldn't be expected to know the correct versions of and check the
 versions of each of them every time MacPorts runs.

 We require users to install versions of MacPorts and Xcode and the Xcode
 command line tools appropriate for the current version of OS X. This is
 amply documented.

 At the time you install MacPorts, it's supposed to verify that Xcode and
 the command line tools are installed, but Mavericks changed the way the
 command line tools work, so our check for whether the command line tools
 were installed no longer detected the case where they were not. I believe
 this has been fixed for the upcoming MacPorts 2.3. See r115900.

 I was considering writing a ProblemHotlist entry for the "unknown load
 command" error since I've seen several tickets for it over the years, and
 I have now done so: ProblemHotlist#malformed-object

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


More information about the macports-tickets mailing list