#50176: Error: org.macports.build for port ld64-latest returned: command execution failed ---------------------------+------------------------ Reporter: fortran_cc@… | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: invalid | Keywords: Port: ld64-latest | ---------------------------+------------------------ Comment (by fortran_cc@…): Replying to [comment:7 jeremyhu@…]:
Please ask for help on the mailing list, so others can chime in and/or benefit.
Finally I managed to make the following command work 'sudo port rev-upgrade' What I did was patiently and repeatedly removing all ports that were reported to be broken from the above command, going from bottom to top, by the command 'sudo port -d -f uninstall XXXX' where XXXX is the culprit package/port that were broken. Originally I had 20 ports broken (not sure why it suddenly had so many broken ports), using the above procedure I got it down to 8 (copy paste below as examples) ---> Found 8 broken port(s), determining rebuild order ---> Rebuilding in order bc @1.06.95 +libedit soprano @2.9.4 kdelibs4 @4.14.3 mobipocket @4.14.3 gpsd @3.14 evince @3.14.2 libkexiv2 @4.14.3 python24 @2.4.6 Then, I applied the same 'sudo port -d -f uninstall' from bottom up, e.g., sudo port -d -f uninstall python24 @2.4.6 until the last one sudo port -d -f uninstall bc @1.06.95 (Btw, I also 'sudo port -d -f uninstall' all the other related versions of the broken ports. Your other installed versions can be seen if you simply use 'sudo port -d -f uninstall' followed by the package name without its version, e.g., sudo port -d -f uninstall python24 ) After going from bottom up and force uninstalling all broken ports, I did 'sudo port selfupdate', and then 'sudo port rev-upgrade' finally went through, reporting no broken ports! It took quite a long time, but I guess it was still a lot faster than removing all macport and then reinstall. But the 'sudo port upgrade outdated' failed in one step, I checked the web and saw only one 2-year old answer which does not solve my problem, I'll report a 'bug' in another thread. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/50176#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X