[MacPorts] #48863: port install perl5: "no destroot found"
#48863: port install perl5: "no destroot found" ----------------------------+-------------------------------- Reporter: jlargentaye@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: perl5 destroot | Port: perl5 ----------------------------+-------------------------------- When I try installing perl5, it fails with "no destroot found". Doing "sudo port clean perl5" does not solve the issue. -- Ticket URL: <https://trac.macports.org/ticket/48863> MacPorts <https://www.macports.org/> Ports system for OS X
#48863: port install perl5: "no destroot found" ----------------------------+-------------------------------- Reporter: jlargentaye@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: perl5 destroot Port: perl5 | ----------------------------+-------------------------------- Comment (by jlargentaye@…): (no logs attached above because I found the solution, but this was troublesome enough I figured I'd leave a trace for the next poor soul who encountered a similiar issue) This is because perl5 is actually a shim frontend to the specific versioned perl package, such as perl5.16 or perl5.18. Solved by doing cleaning perl5.16 directly, then reinstalling: `sudo port clean perl5.16` `sudo port install perl5` -- Ticket URL: <https://trac.macports.org/ticket/48863#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#48863: port install perl5: "no destroot found" ----------------------------+-------------------------------- Reporter: jlargentaye@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: invalid | Keywords: Port: perl5 | ----------------------------+-------------------------------- Changes (by ryandesign@…): * keywords: perl5 destroot => * status: new => closed * resolution: => invalid Comment: Glad you found the solution. Cleaning ''the port that failed to build'' and trying again is the first thing you should always try when a port fails. The port that failed to build is not always the port you asked for. -- Ticket URL: <https://trac.macports.org/ticket/48863#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts