Script Fails With Configure Error
Stunner opened this issue · 5 comments
This is what I get on 2 separate machines running 10.12.16 one running Xcode 9 and the other running Xcode 8.3.3:
$ ./build-libopus.sh
Downloading opus-1.1.3.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 453 100 453 0 0 2189 0 --:--:-- --:--:-- --:--:-- 2199
100 435 100 435 0 0 1125 0 --:--:-- --:--:-- --:--:-- 6126
100 955k 100 955k 0 0 1101k 0 --:--:-- --:--:-- --:--:-- 1101k
Using opus-1.1.3.tar.gz
Building without ccache
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for x86_64-apple-darwin-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking build system type... x86_64-apple-darwin16.7.0
checking host system type... x86_64-apple-darwin
checking how to print strings... printf
checking for style of include used by make... GNU
checking for x86_64-apple-darwin-gcc... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/Users/aaron/Downloads/Opus-iOS-master/build/src/opus-1.1.3':
configure: error: C compiler cannot create executables
See `config.log' for more details
$ open -e config.log
The file /Users/aaron/Downloads/Opus-iOS-master/config.log does not exist.
$
I have this issue too, my problem is the SDKVERSION not equal to my ios sdk version. After modify the SDKVERSION, script works fun.
VERSION="1.2.1"
SDKVERSION="10.3"
MINIOSVERSION="8.0"
@alwayskim, thank you - it helped me)
last Update:
VERSION="1.2.1"
SDKVERSION="11.3"
MINIOSVERSION="8.0"
@iamir4g sorry How's the latest version now?
In case anybody comes across this and wonders what sdk version that they should use, you can use xcodebuild to find out.
In my case below, I would set 17.2 if building for iOS.
`% xcodebuild -showsdks
DriverKit SDKs:
DriverKit 23.2 -sdk driverkit23.2
iOS SDKs:
iOS 17.2 -sdk iphoneos17.2
iOS Simulator SDKs:
Simulator - iOS 17.2 -sdk iphonesimulator17.2
macOS SDKs:
macOS 14.2 -sdk macosx14.2
macOS 14.2 -sdk macosx14.2
tvOS SDKs:
tvOS 17.2 -sdk appletvos17.2
tvOS Simulator SDKs:
Simulator - tvOS 17.2 -sdk appletvsimulator17.2
visionOS SDKs:
visionOS 1.0 -sdk xros1.0
visionOS Simulator SDKs:
Simulator - visionOS 1.0 -sdk xrsimulator1.0
watchOS SDKs:
watchOS 10.2 -sdk watchos10.2
watchOS Simulator SDKs:
Simulator - watchOS 10.2 -sdk watchsimulator10.2`