Changes between Initial Version and Version 1 of Ticket #40699


Ignore:
Timestamp:
Oct 8, 2013, 2:31:32 PM (11 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

"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 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 ​macports-users mailing list.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #40699

    • Property Status changed from new to closed
    • Property Resolution changed from to invalid
    • Property Component changed from ports to base

  • Ticket #40699 – Description

    initial v1  
    22
    33I then did:
     4{{{
    45  sudo port -v upgrade outdated
     6}}}
    57
    68It 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
    79
     10{{{
    811sudo port -v selfupdate
     12}}}
    913
    1014The tail end of that is:
    1115
     16{{{
    1217checking whether the C compiler works... no
    1318configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base':
    … …  
    1722Exit code: 77
    1823Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed
     24}}}
    1925
    2026At this point I have no clue what state I'm in or what to do about it.