#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 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? I have fallen twice now for avoidable tickets (I admit it and go to my corner to shame myself), both connected to me changing back and forth between old laptop and new work machine (including different OS) not remembering state of the installed software base, and twice I got reminded "this is obvious for a developer", but it isn't for me. I read log files if the installation points me to it, but I can't draw the line to "obvious", especially when hidden deep in a dependency, deep in a backtrace on a late stage of the build. I wouldn't expect an obvious error to happen that late. That's why I started writing tickets, otherwise I would have gotten the reinstallation route much earlier, and saved your time. -- Ticket URL: <https://trac.macports.org/ticket/42884#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X