<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
On 1/15/19 7:22 , Ryan Schmidt wrote:
<blockquote
cite="mid:64B762B5-4DBF-4712-B944-339BA9286648@macports.org"
type="cite">
<pre wrap="">On Jan 15, 2019, at 00:18, iEFdev wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">You cannot fetch from GitHub using the curl bundled with a macOS version that old.
</pre>
</blockquote>
<pre wrap="">Would it be possible to link around the problem in any way, if not just temporarily? Just replace curl with a newer did'n't work.
</pre>
</blockquote>
<pre wrap="">Yes, you can build MacPorts from source, and use the --with-curlprefix configure flag to point to a curl library that uses a newer openssl or libressl or other library. Don't use the curl library installed by that MacPorts installation or it will break if you later deactivate the curl port. Instead, use a manually-compiled curl library or a curl library installed by a different MacPorts installation.
</pre>
</blockquote>
Thanks! I think I'll do that later. How does it work with updates,
when it updates itself… it will cont to use my config?<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/15/19 7:48 , Joshua Root wrote:<br>
</div>
<blockquote
cite="mid:da0c612a-ed6a-58a7-ed69-0f8c05e1947c@macports.org"
type="cite">
<pre wrap="">On 2019-1-15 17:18 , iEFdev wrote:
</pre>
<blockquote type="cite">
<pre wrap="">When I run “port fetch” - all I see is port running tclsh5.8... no curl.
</pre>
</blockquote>
<pre wrap="">It uses libcurl.
- Josh
</pre>
</blockquote>
Perfect! That did the trick… for now.<br>
<pre><pre>$ cd /usr/lib && sudo mv libcurl.4.dylib{,.orig}
$ sudo ln -s /opt/local/lib/libcurl.4.dylib .</pre></pre>
At least I can use it for testing and revert back later.<br>
<br>
<br>
· Eric<br>
</body>
</html>