<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 id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On 19 Sep 2024, at 20:46, Joshua Root <jmr@macports.org> wrote:</div><br class="Apple-interchange-newline"><div><div>On 19/9/2024 18:30, Artemio González López wrote:<br><blockquote type="cite">Thanks, Josh! In fact, I renamed the /Library/Developer/CommandLineTools and got most of my ports to succesfully build after executing “sudo port restore —last”. Unfortunately, there is still a problem with libgcc14 that prevents emacs-app to compile:<br>Migration finished with errors.<br> The following ports could not be restored:<br> - emacs<br> Skipped because its dependency libgcc14 failed<br> - emacs-app<br> Skipped because its dependency libgcc14 failed<br> - gnuplot<br> Skipped because its dependency wxWidgets-3.0 failed<br> - julia<br> Skipped because its dependency libgcc14 failed<br> - py311-matplotlib<br> Skipped because its dependency libgcc14 failed<br> - py311-scipy<br> Skipped because its dependency libgcc14 failed<br> - py312-matplotlib<br> Skipped because its dependency libgcc14 failed<br> - py312-scipy<br> Skipped because its dependency libgcc14 failed<br> The following ports could not be fully restored:<br> - py311-jupyter<br> Skipped because its dependency libsodium failed<br> state changed from 'installed' to 'inactive'<br> - py312-jupyter<br> Skipped because its dependency libsodium failed<br> state changed from 'installed' to 'inactive'<br> - py312-jupyterlab<br> Skipped because its dependency libsodium failed<br> state changed from 'installed' to ‘inactive'<br>(There is also a problem with libsodium, but that seems less important). Is this problem known? Does anybody suggest a fix/workaround, while things are ironed out?<br></blockquote><br>A lot has happened since my last reply. We're no longer recommending uninstalling the Command Line Tools, because a more surgical fix has been found: <https://trac.macports.org/wiki/ProblemHotlist#clts16><br><br>I believe gcc14 may be one port that really wants the CLTs, so restoring them would be step 1. One fix for gcc14/libgc14 build failures has already been committed, but there seems to be another one affecting some users. This is the ticket tracking the issues: <https://trac.macports.org/ticket/70641><br><br>If you can't get libgcc14 working in the short term, you should be able to install emacs and emacs-app by turning off the default nativecomp variant.<br><br>As for libsodium, which version did you see the failure with? It was only just updated to 1.0.20.<br><br>- Josh<br></div></div></blockquote></div><div><br></div>Thanks again, Josh!<div><br></div><div>Before reading your message, I deleted the directory /Library/Developer/CommandLineTools and reinstalled the Command Tools for Xcode 16 (which I also have installed) from scratch using the dmg at the Developer website. This should be equivalent to what you propose, since I have checked that the c++ directory is absent from a fresh installation of the Command Line tools:</div><div><br></div><div><p style="margin: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-variant-emoji: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(0, 0, 0);"><span style="font-variant-ligatures: no-common-ligatures">artemio@mbp-13 Downloads % l /Library/Developer/CommandLineTools/usr/include/c++</span></p>
<p style="margin: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-variant-emoji: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(0, 0, 0);"><span style="font-variant-ligatures: no-common-ligatures">ls: /Library/Developer/CommandLineTools/usr/include/c++: No such file or directory</span></p><p style="margin: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-variant-emoji: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(0, 0, 0);"><span style="font-variant-ligatures: no-common-ligatures"><br></span></p></div><div>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></div><div><br></div><div>Thanks a lot,</div><div><br></div><div>Artemio</div><div><br></div><div><br></div><div><br></div></body></html>