#40699: Disastrous port update from Lion to Mountain Lion ----------------------+-------------------------------- Reporter: jeff@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.2.0 Resolution: invalid | Keywords: Port: | ----------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * component: ports => base * resolution: => invalid Old description:

I upgraded from Lion to Mountain Lion (Macbook Pro) with no issues. Then installed Xcode 5, which already had the command line tools set in preferences.

I then did: sudo port -v upgrade outdated

It commented that the file list was outdated and that I might be better to try selfupdate...but continued on its way with the upgrade. The upgrade failed due to a build file not being found, so heeding the suggestion, I tried

sudo port -v selfupdate

The tail end of that is:

checking whether the C compiler works... no configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base': configure: error: C compiler cannot create executables See `config.log' for more details Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base && CC=/usr/bin/cc ./configure --prefix=/opt/local --with- tclpackage=/Library/Tcl --with-install-user=root --with-install- group=admin --with-directory-mode=0755 --enable-readline && make && make install SELFUPDATING=1 Exit code: 77 Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed

At this point I have no clue what state I'm in or what to do about it.

New description: I upgraded from Lion to Mountain Lion (Macbook Pro) with no issues. Then installed Xcode 5, which already had the command line tools set in preferences. I then did: {{{ sudo port -v upgrade outdated }}} It commented that the file list was outdated and that I might be better to try selfupdate...but continued on its way with the upgrade. The upgrade failed due to a build file not being found, so heeding the suggestion, I tried {{{ sudo port -v selfupdate }}} The tail end of that is: {{{ checking whether the C compiler works... no configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base': configure: error: C compiler cannot create executables See `config.log' for more details Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base && CC=/usr/bin/cc ./configure --prefix=/opt/local --with- tclpackage=/Library/Tcl --with-install-user=root --with-install- group=admin --with-directory-mode=0755 --enable-readline && make && make install SELFUPDATING=1 Exit code: 77 Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed }}} At this point I have no clue what state I'm in or what to do about it. -- Comment: "[wiki:FAQ#missingxcode C compiler cannot create executables]" is the most common error you'll see if you haven't installed the command line tools. Xcode does not automatically install or update the command line tools, so please check the preferences window again to make sure your command line tools are installed. You can verify by running "clang -v" and "xcodebuild -version" in the terminal. `xcodebuild` should mention Xcode 5, and `clang` should be version 5 as well. Next, when updating the OS version, you must follow [wiki:Migration migration procedures]. Finally, this issue tracker is for bug reports and feature requests, not technical support. If you need further support, please write to the [https://lists.macosforge.org/mailman/listinfo/macports-users macports- users mailing list]. -- Ticket URL: <https://trac.macports.org/ticket/40699#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X