Opened 4 years ago

Last modified 4 years ago

#61475 assigned defect

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

Reported by: Boose101 Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.6.4
Keywords: Cc:
Port: gmp

Description

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

Attachments (2)

main.log (10.3 KB) - added by Boose101 4 years ago.
Error Log for gmp
config.log (10.3 KB) - added by snarkhunter (Steve Langer) 4 years ago.
Requested config.log

Download all attachments as: .zip

Change History (10)

Changed 4 years ago by Boose101

Attachment: main.log added

Error Log for gmp

comment:1 Changed 4 years ago by 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.

comment:2 Changed 4 years ago by mf2k (Frank Schima)

Milestone: MacPorts 2.7.0
Owner: set to MarcusCalhoun-Lopez
Port: gmp added; Gmp removed
Status: newassigned

comment:3 Changed 4 years ago by Boose101

I am sorry I didn't know.

Last edited 4 years ago by Boose101 (previous) (diff)

comment:4 Changed 4 years ago by mf2k (Frank Schima)

Summary: Failed to configuregmp: configure: error: could not find a working compiler, see config.log for details

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

comment:5 Changed 4 years ago by 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

comment:6 Changed 4 years ago by 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.

Changed 4 years ago by snarkhunter (Steve Langer)

Attachment: config.log added

Requested config.log

comment:7 Changed 4 years ago by 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

comment:8 Changed 4 years ago by 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

Note: See TracTickets for help on using tickets.