Changes between Version 1 and Version 2 of Ticket #44581, comment 43


Ignore:
Timestamp:
Oct 18, 2014, 4:43:31 AM (10 years ago)
Author:
jasoncampisi+macports@…
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #44581, comment 43

    v1 v2  
    662. Reboot the system
    773. Download and build Macports from the latest source (I tried using the binary install route, but the installer hung for over 1hr eating 95% of the CPU cycles; so, I killed the task, and built from the source and installed within 5mins). Guide here [https://guide.macports.org/chunked/installing.macports.html#installing.macports.source guide.macports.org/chunked/installing.macports.html#installing.macports.source]
    8 4. Next, run the command: ''sudo port install cmake''
     84. Run the command: ''sudo port install cmake''
    99
    10 Note: these steps, assume you already installed
     10Note-- these steps assume you already installed:
    11111. Xcode 6
    12122. Xcode 6 Command-line tools and agreed to the Xcode license: ''sudo xcodebuild -license''
    13133. X11 via the XQuartz project [http://xquartz.macosforge.org/ http://xquartz.macosforge.org]
    1414
    15 After investigating the below log fragment, I am left with the question, how do I '''set CMAKE_OSX_DEPLOYMENT_TARGET to empty''', as a means to get around this problem?
     15After investigating the below log fragment, I am left with the question, "How do I '''set CMAKE_OSX_DEPLOYMENT_TARGET to empty''', as a means to get around this problem?"
    1616
    1717My error log includes this detail:[[BR]]