Installing MacPorts on MacOS 10.14 Mojave

Another year, another OS X update.  (Yes, I do copy a fair chunk of the text from previous year’s posts.)  I assume you are here because you downloaded the Mojave Beta/GM from Apple, and were disappointed that there isn’t a MacPorts installer yet.  While I am sure they will release it soon, perhaps we can get you over the hump so you can beat up Mojave before the official drop date.  If you are comfortable compiling software by hand, we should be able to get thru this easy-peasy.

I am doing this on a clean install of Mojave. If you are attempting an upgrade from any previous version, your process may vary in unexpected ways.  If you did an upgrade install, you will want to make sure you’ve downloaded the latest version of Xcode, and you should probably follow the MacPorts uninstall instructions so you have less cruft around that could interfere with the process.  If you have an upgrade issue, please comment here and I’ll do my best to help you out and improve the instructions.

This is my first pass at getting it running.  I’m going to share all my steps.  One or two things I do might be unnecessary, and could be removed later if I refine the process; but I promise I wouldn’t have hit the Publish button if the overall process didn’t work.

  1. Install MacOS “Mojave”
  2. Connect to the internet
  3. Install Xcode 10 from the App Store.
  4. Launch Xcode:
    1. Agree to the license.
    2. Let it install the extra components it says it needs.
    3. Quit xcode.
  5. Open a terminal window:
  6. sudo xcode-select –install
  7. When the pop-up launches, install the command line tools.
  8. cd ~/Desktop
  9. mkdir macports
  10. cd macports
  11. curl -O https://distfiles.macports.org/MacPorts/MacPorts-2.5.3.tar.gz
  12. tar -xzvf MacPorts-2.5.3.tar.gz
  13. cd MacPorts-2.5.3
  14. ./configure
  15. make
  16. sudo make install
  17. echo ‘export PATH=/opt/local/bin:/opt/local/sbin:$PATH’ >> ~/.profile
  18. source ~/.profile
  19. sudo port -v selfupdate

There’s one extra step I find worth doing that isn’t strictly required for installing the MacPort installer tools.  I find it useful to install Java on my machine before I install any ports.  Otherwise you will be plagued with pop-up windows recommending you install Java while compiling ports like rsync.

At this point, you should be ready to start reinstalling your ports! Wee!

After manually installing MacPorts with the above instructions I was able to install rsync, wget, git, python27, which are my usual first validation tests.  Those packages, combined with their dependencies, result in around  75 installed packages; which does a pretty good job of verifying MacPorts is working.  🙂

Updated 2018/09/26 – Tightened up my sloppy use of a root privileged shell after barrykn called me out on it on reddit.  🙂

Updated 2018/10/02 – Fixed the smart-quote thing, so #17 should work now without needed to have the quotes tweaked.

10 Replies to “Installing MacPorts on MacOS 10.14 Mojave”

  1. The ‘uninstall’ link that you posted doesn’t work:

    # port -fp uninstall installed
    Error: Current platform “darwin 18” does not match expected platform “darwin 17”
    Error: If you upgraded your OS, please follow the migration instructions: https://trac.macports.org/wiki/Migration
    OS platform mismatch
    while executing
    “mportinit ui_options global_options global_variations”
    Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch

    1. You are correct. The first part of those instructions, provided by the MacPorts project, do not work if you try to uninstall MacPorts after you upgrade to Mojave. The ‘sudo rm -rf’ command on that page will brute force you into an uninstalled state, which is why I’ve kept the link as part of the instructions.

    2. You can install right over the top of the older version & then issue the remove all packages. Once complete reinstall whatever.

      1. Yup, you can… But I always do my docs from the standpoint of a clean install to reduce the number of comments asking for help caused by some inconsistent crud left around. 🙂

  2. I got this error on line 18:
    $ echo ‘export PATH=/opt/local/bin:/opt/local/sbin:$PATH’ >> ~/.profile
    $ source ~/.profile
    -bash: ‘export: command not found

    1. I am rally sorry about that. It seems WordPress is converting the single quotes in that command into ‘smart quotes’. I’m trying to figure out how to fix that… Copy the command, replace the smart quotes with single quotes, and hit enter. You are also going to need to load ~/.profile into an editor and remove the broken line that was created by the echo with the bad quotes. Technically, you don’t need to remove the line, as it isn’t breaking anything; but you will get an error message every time you open a terminal window if you don’t remove the line, forever reminding you that I suck at WordPress formatting. 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.