From: David Bagonyi <david.bagonyi@...>
The use of `>&` assumes we are using a shell that supports this syntax.
In case of running this through `sh`, we get "Syntax error: Bad fd number"
---
...configure-Fix-compoiler-detection-logic-for-cross-co.patch | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-oe/recipes-devtools/concurrencykit/concurrencykit/0001-configure-Fix-compoiler-detection-logic-for-cross-co.patch b/meta-oe/recipes-devtools/concurrencykit/concurrencykit/0001-configure-Fix-compoiler-detection-logic-for-cross-co.patch
index 6be024662..718f8c19f 100644
--- a/meta-oe/recipes-devtools/concurrencykit/concurrencykit/0001-configure-Fix-compoiler-detection-logic-for-cross-co.patch
+++ b/meta-oe/recipes-devtools/concurrencykit/concurrencykit/0001-configure-Fix-compoiler-detection-logic-for-cross-co.patch
@@ -35,9 +35,9 @@ Signed-off-by: Khem Raj <raj.khem@...>
+ fi
+ assert "$CC" "not found"
+fi
-+if `$CC --version | grep gcc >& /dev/null`; then
++if `$CC --version | grep gcc > /dev/null 2>&1`; then
+ COMPILER=gcc
-+elif `$CC --version | grep clang >& /dev/null`; then
++elif `$CC --version | grep clang > /dev/null 2>&1`; then
+ COMPILER=clang
+else
+ COMPILER="not-found"
--
2.17.1
