From 86b1376e5ca96672154bea868a026790c941c0a6 Mon Sep 17 00:00:00 2001
From: Christian Kandeler <christian.kandeler@qt.io>
Date: Thu, 4 Apr 2019 16:42:05 +0200
Subject: [PATCH] Do not set up the "clang" binary as a C++ compiler

"clang" behaves differently than "clang++", even if it is the same file.
In particular, "clang" will not properly act as a linker for C++
projects.

Change-Id: I1654ccec0755c9b4534cc2be06de03c5d6bc42d2
Reviewed-by: hjk <hjk@qt.io>
---
 src/plugins/projectexplorer/gcctoolchain.cpp | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/src/plugins/projectexplorer/gcctoolchain.cpp b/src/plugins/projectexplorer/gcctoolchain.cpp
index 4eba54e08e5..e9d6490b3bc 100644
--- a/src/plugins/projectexplorer/gcctoolchain.cpp
+++ b/src/plugins/projectexplorer/gcctoolchain.cpp
@@ -1449,9 +1449,6 @@ QList<ToolChain *> ClangToolChainFactory::autoDetect(const QList<ToolChain *> &a
     if (!compilerPath.isEmpty()) {
         const FileName clang = compilerPath.parentDir().appendPath(
                     HostOsInfo::withExecutableSuffix("clang"));
-        tcs.append(autoDetectToolchains(clang,
-                                        hostAbi, Constants::CXX_LANGUAGE_ID,
-                                        Constants::CLANG_TOOLCHAIN_TYPEID, alreadyKnown));
         tcs.append(autoDetectToolchains(clang,
                                         hostAbi, Constants::C_LANGUAGE_ID,
                                         Constants::CLANG_TOOLCHAIN_TYPEID, alreadyKnown));