Clang config issues after update to Xcode 13.1 on Big Sur

[Ryan Schmidt]

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
> 
> 
> Errors seen in
> 
> configure:6360: checking whether the compiler is clang
> configure:6382: /usr/bin/clang -c -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
> conftest.c:12:12: error: unknown type name 'barfbarf'
>            barfbarf
>            ^
> 1 error generated.
> configure:6382: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> 
> And
> configure:6629: result: no
> configure:6629: checking for sys/systeminfo.h
> configure:6629: /usr/bin/clang -c -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 -I/opt/local/include -isysroot/Library/Dev
> eloper/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
> conftest.c:48:10: fatal error: 'sys/systeminfo.h' file not found
> #include <sys/systeminfo.h>
>          ^~~~~~~~~~~~~~~~~~
> 1 error generated.
> configure:6629: $? = 1
> 
> And
> 
> configure:6629: /usr/bin/clang -c -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
> conftest.c:48:10: fatal error: 'coff.h' file not found
> #include <coff.h>
>          ^~~~~~~~
> 1 error generated.
> configure:6629: $? = 1
> 
> And
> 
> configure:6629: /usr/bin/clang -c -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
> conftest.c:48:10: fatal error: 'pty.h' file not found
> #include <pty.h>
>          ^~~~~~~
> 1 error generated.
> configure:6629: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> 
> And
> 
> configure:6629: /usr/bin/clang -c -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 -I/opt/local/include -isysroot/Library/Dev
> eloper/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
> conftest.c:59:10: fatal error: 'vfork.h' file not found
> #include <vfork.h>
>          ^~~~~~~~~
> 1 error generated.
> configure:6629: $? = 1
> 
> 
> And
> 
> loper/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
> conftest.c:61:10: fatal error: 'stdio_ext.h' file not found
> #include <stdio_ext.h>
>          ^~~~~~~~~~~~~
> 1 error generated.
> 
> And perhaps a couple others.

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).