From 86a124e9d5cb3155060f25daa28ca4983f9556cd Mon Sep 17 00:00:00 2001
From: Andre Maroneze <andre.maroneze@cea.fr>
Date: Tue, 7 Feb 2023 21:17:15 +0100
Subject: [PATCH] [e-acsl] change order of CPPFLAGS
Since CPPFLAGS are user-customizable (via '-e'), putting them after CFLAGS
allows users to override some default flags (e.g. -O2, -g).
---
src/plugins/e-acsl/scripts/e-acsl-gcc.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/plugins/e-acsl/scripts/e-acsl-gcc.sh b/src/plugins/e-acsl/scripts/e-acsl-gcc.sh
index ae3dbbf7c2c..ec919b1aa43 100755
--- a/src/plugins/e-acsl/scripts/e-acsl-gcc.sh
+++ b/src/plugins/e-acsl/scripts/e-acsl-gcc.sh
@@ -1105,7 +1105,7 @@ if [ -n "$OPTION_COMPILE" ]; then
# by a user
if [ -n "$OPTION_INSTRUMENT" ]; then
if [ -z "$OPTION_INSTRUMENTED_ONLY" ]; then
- ($OPTION_ECHO; $CC $CPPFLAGS $CFLAGS "$@" -o "$OUTPUT_EXEC" $LDFLAGS);
+ ($OPTION_ECHO; $CC $CFLAGS $CPPFLAGS "$@" -o "$OUTPUT_EXEC" $LDFLAGS);
error "fail to compile/link un-instrumented code" $?;
fi
# If $OPTION_INSTRUMENT is unset then the sources are assumed to be already
--
GitLab