#48178: circular dependency apple-gcc42/xpm, and many others --------------------------+-------------------------------- Reporter: herzog@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: apple-gcc42 | --------------------------+-------------------------------- Changes (by ryandesign@…): * cc: jeremyhu@… (added) * status: new => closed * resolution: => fixed Comment: Thanks for confirming. I've updated the apple-gcc42 port to require Xcode 2.5 in r151945. Presumably it would be no problem to go back to an older Xcode now if you wanted to. Of course, if MacPorts publishes an update for apple-gcc42, you'll need Xcode 2.5 again to build it. Software installed with MacPorts is designed to be used on the computer and OS on which it was installed. You should not, for example, use MacPorts installed on an external drive attached to a PowerBook G4 running Tiger to install some ports, then move that external drive to a MacBook Pro running El Capitan and expect the software you installed with MacPorts on Tiger to be usable there. But if you mean just running MacPorts-installed software from another disk, on the same computer and same OS version, then that's more likely to work. MacPorts and Xcode are not needed to run the software that was installed, only to install it in the first place. You may need to account for different paths, however. If you installed software on your startup disk using MacPorts in /opt/local, and then later boot up from a different disk, now MacPorts is no longer at /opt/local but is instead at /Volumes/YourDiskName/opt/local. Most software installed with MacPorts can't be run from another path; you'll get an error that libraries can't be found at the original /opt/local/... path. The simple workaround for this problem is to create an appropriate /opt/local symlink on your new boot disk. For example: {{{ sudo mkdir -p /opt cd /opt sudo ln -s /Volumes/YourDiskName/opt/local local }}} Before you do this, if YourDiskName contains spaces or other special characters, use the Finder to rename it so that it doesn't. For example, if the disk you have MacPorts on is named "Macintosh HD", rename it to e.g. "MacintoshHD". -- Ticket URL: <https://trac.macports.org/ticket/48178#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X