aboutsummaryrefslogtreecommitdiffstats
path: root/projects
diff options
context:
space:
mode:
authorDmitri Gribenko <gribozavr@gmail.com>2013-01-09 15:25:30 +0000
committerDmitri Gribenko <gribozavr@gmail.com>2013-01-09 15:25:30 +0000
commita7303360aea203d0f58f77ac43287f5b98c7cbe6 (patch)
tree0e31b2f98bd583ad86d8bcb1694fbbf1db0a72ce /projects
parent7bf2e1b9ef797fda5de53956a1d2aea900ce794f (diff)
downloadexternal_llvm-a7303360aea203d0f58f77ac43287f5b98c7cbe6.zip
external_llvm-a7303360aea203d0f58f77ac43287f5b98c7cbe6.tar.gz
external_llvm-a7303360aea203d0f58f77ac43287f5b98c7cbe6.tar.bz2
Configure: if we compile with clang, check that it is not broken
Some linux distibutions (for example, Mageia 2, Fedora 17) ship Clang that is essentially broken for the end user. Clang can not find or compile libstdc++ headers. The issue is that our configure prefers clang over gcc, thus selecting a broken Clang when a working GCC is available. Now we detect this issue by compiling a simple program. If it does not compile, configure stops with an error suggesting the user to select a different compiler. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@171975 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'projects')
0 files changed, 0 insertions, 0 deletions