From d4f15a5be4004a93d38597cd89d798144dc10dca Mon Sep 17 00:00:00 2001
From: Lars Knoll <lars.knoll@theqtcompany.com>
Date: Fri, 15 Apr 2016 08:09:33 +0200
Subject: [PATCH] Remove the configure notice about unknown architectures

With 5.7, we can rely on c++11 atomics (or the msvc ones), so
the note doesn't make sense anymore.

Change-Id: I10cc67f3dd840f3272ca975c2c9120a8c871a2fb
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
---
 configure | 23 -----------------------
 1 file changed, 23 deletions(-)

diff --git a/configure b/configure
index fc0639ab8e..9bb3f215d2 100755
--- a/configure
+++ b/configure
@@ -7124,29 +7124,6 @@ rm -f "$QMAKE_VARS_FILE" 2>/dev/null
 
 ) || exit
 
-#-------------------------------------------------------------------------------
-# check for platforms that we don't yet know about
-#-------------------------------------------------------------------------------
-if [ "$CFG_ARCH" = "unknown" ]; then
-cat <<EOF
-
-        NOTICE: configure was unable to determine the architecture
-        for the $XQMAKESPEC target.
-
-        Qt will not use a specialized implementation for any atomic
-        operations. Instead a generic implemention based on either GCC
-        intrinsics or C++11 std::atomic<T> will be used (when
-        available). The generic implementations are generally as fast
-        as and always as safe as a specialized implementation.
-
-        If no generic implementation is available, Qt will use a
-        fallback UNIX implementation which uses a single
-        pthread_mutex_t to protect all atomic operations. This
-        implementation is the slow (but safe) fallback implementation
-        for architectures Qt does not yet support.
-EOF
-fi
-
 #-------------------------------------------------------------------------------
 # finally save the executed command to another script
 #-------------------------------------------------------------------------------