build-script: force LLVM to use libc++ on Darwin #1175
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rdar://problem/24452118
|
@swift-ci Please test |
|
@bitjammer Could you review for Swift 2.2? |
|
LGTM. |
|
The failure was unrelated: |
gribozavr
added a commit
that referenced
this pull request
Feb 3, 2016
build-script: force LLVM to use libc++ on Darwin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Under certain circumstances, when the OS X machine has the
/usr/includedirectory that contains stale headers (not from the current Xcode installation), the build might fail. This patch works around the issue by ensuring that LLVM CMake scripts don't try to look in/usr/include.rdar://problem/24452118