<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="">Thanks for the help. I was able to get things working with latest Big Sur 11.6.1 && Xcode 13.1 && CLT for Xcode 13.1 by: <div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>a) removing everything from /opt/local</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>b) install package “maxOS Big Sur v11” from the “Installing Macports” page, <a href="https://www.macports.org/install.php" class="">https://www.macports.org/install.php</a></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>c) reinstall my packages, and instead of “port install emacs-devel +x11” doing the simple emacs with</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>port install emacs +x11</div><div class=""><br class=""></div><div class="">I did not even try the “emacs-devel” because I was running the “level” version only because I was seeing issues with trying to install the simple “emacs” with my new M1 Mac mini.</div><div class="">Before blowing away /opt/local I was able to install emacs +x11 but the emacs-devel +x11 was still showing the config issues.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">jw</div><div class=""><br class=""></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 5, 2021, at 10:39 AM, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Oct 28, 2021, at 08:05, John Wiggins wrote:<br class=""><blockquote type="cite" class=""><br class="">It seemed to work yesterday under Xcode 13.0 and its CLT.<br class="">Now emacs-dev seems to fail after update to Xcode 13.1 and CLT for Xcode 13.1.<br class=""><br class="">I am a bit of a novice, doe the following in<br class=""> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_emacs/emacs-devel/work/emacs-20211020/config.log<br class="">Mean that I merely need to wait until the macports tools are updated to Xcode 13.1?<br class=""><br class="">Thanks in advance.<br class="">John<br class=""><br class="">…snip...</blockquote><br class="">It's difficult to make a diagnosis just based on what you've shown. The purpose of a configure script is to determine the capabilities of your operating system. It can be normal for errors to appear in the config.log. I do not know if these specific errors are normal for this specific port or for your OS version, whatever that is. On my macOS 10.13 system none of the files mentioned in those errors exist, so probably those errors are normal, and the type name "barfbarf" certainly sounds like something used for testing. Usually if a port fails to build you should file a bug report and attach the main.log (and if it is a configuration failure also the config.log).<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>