From def07f630605f7014e4f80c511be4d8f9eca8d95 Mon Sep 17 00:00:00 2001
From: Fabian Kosmale <fabian.kosmale@qt.io>
Date: Mon, 25 Mar 2024 11:36:09 +0100
Subject: [PATCH] VxWorks: Skip fstack-protector-strong

We do not know yet why it fails exactly to link, and what a proper fix
would be. For now, unconditionally disable it so that we can get
submodule updates in again.

Task-number: QTBUG-123715
Change-Id: I832cc8801c7fcb4b0a755aa4ff0bc65d15bf8230
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
---
 configure.cmake | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/configure.cmake b/configure.cmake
index d99e2c0afec..942c359c0dd 100644
--- a/configure.cmake
+++ b/configure.cmake
@@ -420,9 +420,12 @@ alloca(1);
 ")
 
 # stack_protector
-if(NOT WASM)
+if(NOT WASM AND NOT VXWORKS)
     # emcc doesn't support this, but the detection accidentally succeeds
     # https://github.com/emscripten-core/emscripten/issues/17030
+
+    # VXWORKS: We currently don't know the correct linker options. This is
+    # tracked at QTBUG-123715
     qt_config_compiler_supports_flag_test(stack_protector
         LABEL "stack protection"
         FLAG "-fstack-protector-strong"