<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><div><blockquote type="cite"><div>On 20 Sep 2024, at 01:07, Joshua Root <jmr@macports.org> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><blockquote type="cite" style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class="Apple-interchange-newline">Unfortunately, after executing supo port restore —last I got exactly the same error as before (libgcc14 and lib sodium failed, and cause several ports, like emacs-app, not to compile). I do not know what else to do. Could executing "sudo port selfupdate” before “sudo port restore —last” help, or could it mess up things with the ports that have been deactivated by the previous restore commands? Is there anything else I should try? By the way, I am running things on a 2019 M1 13” MacBook Pro.<br></blockquote><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">You should definitely run port selfupdate, because that is how you get the latest changes to the ports, which includes the fixes for many of the Sequoia and Xcode 16 problems.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">- Josh</span></div></blockquote><br></div><div>Hi, Josh,</div><div><br></div><div>I just ran port selfupdate, but the only outdated port it found is xorg-libXi (which I updated). I guess it is not worth to give port restore —last another try, since the problematic por was libgcc14, which hasn’t¡t been updated. Am I right? I would also like to know whether anybody else who, like me, got rid of the c++ directory one way or another (and with an M1 chip) is having the same problem with libgcc14. If this is the case perhaps something else is going on, apart from the rogue c++ directory problem.</div><div><br></div><div>Thanks again for your help,</div><div><br></div><div>Artemio</div><br>
<br></body></html>