#16500: Error building MacPorts_Framework ----------------------------------+----------------------------------------- Reporter: dstwo@princeton.edu | Owner: armahg@macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: Port: MacPorts_Framework | ----------------------------------+----------------------------------------- Comment(by dstwo@princeton.edu): Yep, it worked. I'm actually not sure why the framework was installed on my machine - perhaps it was a dependency of something? {{{ ~ $ sudo port selfupdate Password: MacPorts base version 1.600 installed Downloaded MacPorts base version 1.600 The MacPorts installation is not outdated and so was not updated selfupdate done! ~ $ sudo port upgrade outdated Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/dsn/Research/PrimShell/trunk"). Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. (you might also see this message if a pseudo-port such as outdated or installed expands to no ports). Error: No port found. ~ $ sudo port install MacPorts_Framework Password: Portfile changed since last build; discarding previous state. ---> Fetching MacPorts_Framework ---> Verifying checksum(s) for MacPorts_Framework ---> Extracting MacPorts_Framework ---> Configuring MacPorts_Framework ---> Building MacPorts_Framework ---> Staging MacPorts_Framework into destroot ---> Installing MacPorts_Framework 0.1.0_0 ---> Activating MacPorts_Framework 0.1.0_0 ---> Cleaning MacPorts_Framework }}} -- Ticket URL: <http://trac.macports.org/ticket/16500#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS