`port install' from github tarball fails

Ken Cunningham ken.cunningham.webuse at gmail.com
Tue Sep 25 15:35:12 UTC 2018

Don't be put off too much by this. It takes only about 10 minutes to fix, if you care to. I use it on every machine < 10.9 routinely.

Download the macports source tarball. You'll use it twice.

First disable any PATH settings in your .profile. Then configure a "bootstrap" installation of macports that will hold a modern SSL:

./configure --with-prefix=/opt/bootstrap  --with-applications-dir=/opt/bootstrap/Applications
make && sudo make install

Then use that installation to install a current version of curl

sudo /opt/bootstrap/bin/port -v -N install curl

Once it's finished, start with a fresh copy of the macports source, and tell it to use the new curl

./configure --with-curlprefix=/opt/bootstrap
make && sudo make install

it will write a new copy of macports over your old copy in /opt/local, keeping all your settings and installed ports intact.

Then re-enable your PATH settings in .profile

There is one hiccup. Updating macports with "sudo port selfupdate" does not respect the curlprefix. 

So instead, "sync" macports instead of "selfupdating" it

sudo port -v sync

When you want to update MacPorts, build a copy from source against /opt/bootstrap.

Once in a while, as often as you feel you need to, update curl in /opt/bootstrap.


On 2018-09-25, at 2:35 AM, Mojca Miklavec wrote:

> Dear Werner,
> Lion does not properly support HTTPS. You might need to recompile
> MacPorts from source to link against a version of libcurl with full
> SSL support.
> See for example:
>    https://trac.macports.org/ticket/51516
> Mojca

More information about the macports-users mailing list