gmp: configure: error: could not find a working compiler, see config.log for details

[Boose101]

Error: Failed to configure gmp, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gmp/gmp/work/gmp-6.2.0/config.log
Error: Failed to configure gmp: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gmp/gmp/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port gmp failed

[Boose101]

Error Log for gmp

[mf2k (Frank Schima)]

The Milestone field is for use by Macports team members only, please do not set it.

In the future, please add the port maintainer(s) to Cc (port info --maintainers gmp), if any.

[Boose101]

I am sorry I didn't know.

[mf2k (Frank Schima)]

Error is:

:info:configure checking compiler /usr/bin/clang -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk  -I/opt/local/include... no
:info:configure configure: error: could not find a working compiler, see config.log for details

[snarkhunter (Steve Langer)]

I'm seeing this same error on a Catalina system on which I had upgraded Xcode to 12.2. I then saw that we were advised not to do that yet, so I downloaded Xcode 11.7 and used xcode-select to choose it. I am *not* having this problem on another Catalina system that was never upgraded to 12.2. I have not seen the problem on other ports on the system that was temporarily upgraded.

Both systems build everything from source because I need to use a non-standard location for ports.

-- Steve

[kencu (Ken)]

To sort this out, we'd need to look at the config.log, and see the lines of code that failed to compile that triggered this error. The explanation will likely be there.

[snarkhunter (Steve Langer)]

Requested config.log

[snarkhunter (Steve Langer)]

I attached port work gmp/gmp-6.2.1/config.log The error seems to be

configure:5847: /usr/bin/clang -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -c conftest.c >&5
xcrun: error: unable to exec Xcode native xcrun (Permission denied).
configure:5850: $? = 1
configure:5869: /usr/bin/clang -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk 2>&1 | grep xlc >/dev/null
configure:5872: $? = 1
configure:5926: checking compiler /usr/bin/clang -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk  -I/opt/local/stow/ports-quartz/include
Test compile: 
configure:5940: /usr/bin/clang -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk  -I/opt/local/stow/ports-quartz/include conftest.c >&5
xcrun: error: unable to exec Xcode native xcrun (Permission denied).
configure:5943: $? = 1
failed program was:

int main () { return 0; }
configure:7030: result: no
configure:7268: error: could not find a working compiler, see config.log for details

[snarkhunter (Steve Langer)]

My problem seems to have been fixed by moving Xcode from $HOME/Applications to /Applications and re-running xcode-select -s. I didn't see anything in the instructions saying that Xcode couldn't be installed under $HOME.

-- Steve