which carthage: /usr/local/bin/carthagecarthage version: 0.33.0xcodebuild -version: Build version 11M374r--no-build? no--no-use-binaries? no--use-submodules? no--cache-builds? no--new-resolver? noCartfile
<YOUR CARTFILE>
github "soffes/CommonCrypto"
github "soffes/Crypto"
github "MagicalPanda/MagicalRecord"
github "timbueno/TBDirectoryKit"
github "https://github.com/dropbox/SwiftyDropbox" ~> 5.0.0
github "timbueno/GCDWebServer" ~> 3.3.34
github "ashleymills/Reachability.swift" ~> 4.0
github "shinydevelopment/SimulatorStatusMagic" ~> 1.9.2
github "PierrePerrin/ShadowView"
Carthage Output
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
** ARCHIVE FAILED **
The following build commands failed:
Ld /Users/tim/Library/Caches/org.carthage.CarthageKit/DerivedData/11.0_11M374r/Alamofire/4.8.2/Build/Intermediates.noindex/ArchiveIntermediates/Alamofire\ iOS/IntermediateBuildFilesPath/Alamofire.build/Release-iphoneos/Alamofire\ iOS.build/Objects-normal/arm64/Binary/Alamofire normal arm64
(1 failure)
Build Failed
Task failed with exit code 65:
/usr/bin/xcrun xcodebuild -workspace /Users/tim/Projects/Bound/Carthage/Checkouts/Alamofire/Alamofire.xcworkspace -scheme Alamofire\ iOS -configuration Release -derivedDataPath /Users/tim/Library/Caches/org.carthage.CarthageKit/DerivedData/11.0_11M374r/Alamofire/4.8.2 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/tl/v7ygpjb93xgbk8mz478x769m0000gn/T/Alamofire SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/tim/Projects/Bound/Carthage/Checkouts/Alamofire)
This usually indicates that project itself failed to compile.
Actual outcome
Carthage fails to compile dependencies after updating to Xcode 11 Beta 4.
Expected outcome
Carthage should compile these dependencies.
I think I'm seeing a similar issue and the source of the problem is Xcode. If you look through the log file are there references to Swift methods not being found?
I also found this issue, platform Mac no this issue .
I also found this issue, platform Mac no this issue .
MacOS Schemes are building just fine on mine as well...
I think I'm seeing a similar issue and the source of the problem is Xcode. If you look through the log file are there references to Swift methods not being found?
ld: warning: Could not find or use auto-linked library 'swiftFoundation'
ld: warning: Could not find or use auto-linked library 'swiftDarwin'
ld: warning: Could not find or use auto-linked library 'swiftCoreGraphics'
ld: warning: Could not find or use auto-linked library 'swiftCore'
ld: warning: Could not find or use auto-linked library 'swiftCoreFoundation'
ld: warning: Could not find or use auto-linked library 'swiftObjectiveC'
ld: warning: Could not find or use auto-linked library 'swiftDispatch'
I'm not sure if that is what you were asking about or not though...
Yes, that is the same thing I'm seeing when trying to archive a framework directly from Xcode. Haven't found a workaround yet.
Looks like Xcode can't find the Swift standard libraries for phone or watch architectures.
Found the workaround via Twitter: https://twitter.com/krzyzanowskim/status/1151549874653081601?s=21
So, not a Carthage issue :)
To solve the issue create a workaround.xcconfig file. This file can live elsewhere - like your desktop.
LD_VERIFY_BITCODE=NO
Then doing the following should work
XCODE_XCCONFIG_FILE=/Users/SomeUser/SomeDirectory/Project/workaround.xcconfig carthage update platform iOS
Setting a custom xcconfig file didn't work for me, so I whipped up a small ruby script to add the build setting, you have to run it after updating, and then just tell carthage to build. This may save some time for someone.
https://gist.github.com/octover/fd7da48cd35794cc5f1766031ccc7994
Actually the xcconfig file worked for me, it just had to be an absolute path and not relative, that would be much easier to do what @kaandedeoglu suggested.
As suggested by @jdhealy in a private conversation the best workaround is:
1) Create a Xcode11Beta4Fix.xcconfig containing:
LD_VERIFY_BITCODE__XCODE_PRODUCT_BUILD_VERSION_11M374r=NO
LD_VERIFY_BITCODE=$(LD_VERIFY_BITCODE__XCODE_PRODUCT_BUILD_VERSION_$(XCODE_PRODUCT_BUILD_VERSION))
2) Then
XCODE_XCCONFIG_FILE=/absolute/path/to/Xcode11Beta4Fix.xcconfig carthage update --platform iOS
All credit to @jdhealy
Workaround is not working.
@ajmeerkhan are you using an absolute path? Did you name the variables correctly? Are you using beta4 ? It ONLY works on beta4
@tmspzz yes am using the absolute path, and naming variables are correct, and off course using beta 4
@ajmeerkhan try following other suggestions in the thread. Or wait for the next beta. This is not a Carthage issue.
@tmspzz Totally unrelated, but looking to install some dependencies for Xcode 11 & Swift 5.1
I cloned the Carthage repo and ran make install, but got an error. Below is the error output, could you point me in the right direction to successfully run make install?
Stack dump:
let dependenciesUsage = "the dependency names to update, checkout and build"
return curry(Options.init)
<*> mode <| Option(key: "checkout", defaultValue: true, usage: "skip the checking out of dependencies after updating")
<*> mode <| Option(key: "build", defaultValue: true, usage: buildDescription)
<*> mode <| Option(key: "verbose", defaultValue: false, usage: "print xcodebuild output inline (ignored if --no-build option is present)")
<*> mode <| Option(key: "log-path", defaultValue: nil, usage: "path to the xcode build output. A temporary file is used by default")
<*> mode <| Option(key: "new-resolver", defaultValue: false, usage: "use the new resolver codeline when calculating dependencies. Default is false")
<*> BuildOptions.evaluate(mode, addendum: "\n(ignored if --no-build option is present)")
<*> CheckoutCommand.Options.evaluate(mode, dependenciesUsage: dependenciesUsage)
"
@tmspzz @DavidBrunow I clone your repo from https://github.com/Shepherd-Dog/Carthage.git, ran make install and still got the same error. Are there any prerequisite needed for a successful install?
@henrysaintjuste Please see #2831
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Same Issue With Xcode 11.1 (11a1027)
Workaround listed does not work
@pacu, are you seeing The following build commands failed: 卢 Ld /Users and then Task failed with exit code 65?
And, if so, could you file a new issue with at least a subset of your dependencies?
thanks it's open under #2888
I had originally created an issue on swift-grpc thinking there was something wrong on that side. grpc/grpc-swift#604
Most helpful comment
To solve the issue create a
workaround.xcconfigfile. This file can live elsewhere - like your desktop.Then doing the following should work