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:
a) removing everything from /opt/local
b) install package “maxOS Big Sur v11” from the “Installing Macports”
page, https://www.macports.org/install.php
<https://www.macports.org/install.php>
c) reinstall my packages, and instead of “port install emacs-devel
+x11” doing the simple emacs with
port install emacs +x11
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.
Before blowing away /opt/local I was able to install emacs +x11 but the
emacs-devel +x11 was still showing the config issues.
Thanks,
jw
> On Nov 5, 2021, at 10:39 AM, Ryan Schmidt <[email protected]> wrote:
>
> On Oct 28, 2021, at 08:05, John Wiggins wrote:
>>
>> It seemed to work yesterday under Xcode 13.0 and its CLT.
>> Now emacs-dev seems to fail after update to Xcode 13.1 and CLT for Xcode
>> 13.1.
>>
>> I am a bit of a novice, doe the following in
>> /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
>> Mean that I merely need to wait until the macports tools are updated to
>> Xcode 13.1?
>>
>> Thanks in advance.
>> John
>>
>> …snip...
>
> 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).
>
