<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hello,<div class=""><br class=""></div><div class=""><div style="color: rgb(14, 16, 26); margin-top: 0pt; margin-bottom: 0pt;" class=""><span data-preserver-spaces="true" style="margin-top: 0pt; margin-bottom: 0pt;" class="">I am in the same boat (and have switched from HomeBrew to MacPorts a few weeks ago, so, maybe I am wrong). </span></div><div style="color: rgb(14, 16, 26); margin-top: 0pt; margin-bottom: 0pt;" class=""><span data-preserver-spaces="true" style="margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></span></div><div style="color: rgb(14, 16, 26); margin-top: 0pt; margin-bottom: 0pt;" class=""><span data-preserver-spaces="true" style="margin-top: 0pt; margin-bottom: 0pt;" class="">MacPorts as a tool works just fine on Macs with Apple Silicon, but many ports are “broken” and have to be fixed. Most of them just do not compile for `arm64`, and it is not MacPorts fault, some - do not compile due to MacPorts configuration (rare cases). So far, as far as I understand, the best course of action is to report all broken ports to the MacPorts tracker and to developers of the tool that does not compile for `arm64` arch. For example, this is a ticket about broken Neovim (</span><a target="_blank" href="https://trac.macports.org/ticket/61550" class="editor-rtfLink" style="margin-top: 0pt; margin-bottom: 0pt; color: rgb(74, 110, 224);"><span data-preserver-spaces="true" style="margin-top: 0pt; margin-bottom: 0pt;" class="">https://trac.macports.org/ticket/61550</span></a><span data-preserver-spaces="true" style="margin-top: 0pt; margin-bottom: 0pt;" class="">), but it does not compile due to issues on the NeoVim side (that’s why I started a discussion with them (</span><a target="_blank" href="https://github.com/neovim/neovim/issues/13399" class="editor-rtfLink" style="margin-top: 0pt; margin-bottom: 0pt; color: rgb(74, 110, 224);"><span data-preserver-spaces="true" style="margin-top: 0pt; margin-bottom: 0pt;" class="">https://github.com/neovim/neovim/issues/13399</span></a><span data-preserver-spaces="true" style="margin-top: 0pt; margin-bottom: 0pt;" class="">).</span></div><div style="color: rgb(14, 16, 26); margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="color: rgb(14, 16, 26); margin-top: 0pt; margin-bottom: 0pt;" class=""><span data-preserver-spaces="true" style="margin-top: 0pt; margin-bottom: 0pt;" class="">I use the following `make` target to install MacPorts on Apple Silicon or you can just download the package from the site (<a href="https://www.macports.org/install.php" class="">https://www.macports.org/install.php</a></span>):</div></div><div class=""><br class=""></div><div class="">```</div><div class=""><div class="">macports: ## Install/Upgrade MacPorts</div><div class="">ifeq (, $(shell which port))</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>$(eval TEMP_PKG := $(shell mktemp -t macports).pkg)</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>curl --silent --output $(TEMP_PKG) --remote-name <a href="https://distfiles.macports.org/MacPorts/MacPorts-2.6.4_1-11-BigSur.pkg" class="">https://distfiles.macports.org/MacPorts/MacPorts-2.6.4_1-11-BigSur.pkg</a> </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>sudo installer -pkg $(TEMP_PKG) -target /</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>rm -Rf $(TEMP_PKG)</div><div class="">endif</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>sudo port selfupdate</div><div class="">```</div><div class=""><br class=""></div><div class="">Most of the tools I use just work:</div><div class=""><br class=""></div><div class="">```</div><div class=""><div class="">The following ports are currently installed:</div><div class=""> autoconf @2.69_5 (active)</div><div class=""> automake @1.16.3_0 (active)</div><div class=""> carthage @0.35.0_0 (active)</div><div class=""> fish @3.1.2_0 (active)</div><div class=""> fzf @0.24.3_0 (active)</div><div class=""> gettext @0.19.8.1_2 (active)</div><div class=""> icu @67.1_2 (active)</div><div class=""> ninja @1.10.1_0 (active)</div><div class=""> tig @2.5.1_0+doc (active)</div><div class=""> tmux @3.1c_0 (active)</div></div><div class="">``</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Artem</div><div><br class=""><blockquote type="cite" class=""><div class="">On 27 Nov 2020, at 15:37, Jeffrey Walton <<a href="mailto:noloader@gmail.com" class="">noloader@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Fri, Nov 27, 2020 at 10:27 AM Giovanni Cantele<br class=""><<a href="mailto:giovanni.cantele@spin.cnr.it" class="">giovanni.cantele@spin.cnr.it</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">Dear All,.<br class=""><br class="">I’m searching the web but I cannot find any response to the following question:<br class=""><br class="">is there any ongoing project for porting the whole macports staff on the new Apple silicon architecture?<br class="">What happens to those who extensively make use of macports and have bought the recent released MacBook Pro running on the new processors?<br class=""></blockquote><br class="">There are several recent threads about support of the latest hardware<br class="">and software at:<br class=""><br class=""> * <a href="https://lists.macports.org/pipermail/macports-users/2020-November/thread.html" class="">https://lists.macports.org/pipermail/macports-users/2020-November/thread.html</a><br class=""><br class="">I understand Macports is working through the issues as they encounter<br class="">them during testing before a release.<br class=""><br class="">I'm guessing it is a bigger task than just supporting a new OS release.<br class=""><br class="">Jeff<br class=""></div></div></blockquote></div><br class=""></div></body></html>