diff options
Diffstat (limited to 'meta/recipes-core/kbd/kbd/fix_cflags.patch')
-rw-r--r-- | meta/recipes-core/kbd/kbd/fix_cflags.patch | 25 |
1 files changed, 0 insertions, 25 deletions
diff --git a/meta/recipes-core/kbd/kbd/fix_cflags.patch b/meta/recipes-core/kbd/kbd/fix_cflags.patch deleted file mode 100644 index 37220960ab..0000000000 --- a/meta/recipes-core/kbd/kbd/fix_cflags.patch +++ /dev/null | |||
@@ -1,25 +0,0 @@ | |||
1 | We need to ensure our CFLAGS are preserved as well as whatever tweak configure | ||
2 | tries to make. Without these, the debug prefix changes get lost and we lose | ||
3 | build reproducibility, likely with other side effects. | ||
4 | |||
5 | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> | ||
6 | Upstream-Status: Pending | ||
7 | 2020/1/27 | ||
8 | |||
9 | Index: kbd-2.2.0/configure.ac | ||
10 | =================================================================== | ||
11 | --- kbd-2.2.0.orig/configure.ac | ||
12 | +++ kbd-2.2.0/configure.ac | ||
13 | @@ -72,9 +72,9 @@ if test "$enable_code_coverage" = yes; t | ||
14 | fi | ||
15 | |||
16 | case "$GCC,$ac_cv_prog_cc_g" in | ||
17 | - yes,yes) CFLAGS="-g $CC_O_LEVEL $FORTIFY_SOURCE" ;; | ||
18 | - yes,) CFLAGS="$CC_O_LEVEL $FORTIFY_SOURCE" ;; | ||
19 | - ,yes) CFLAGS="-g" ;; | ||
20 | + yes,yes) CFLAGS="-g $CC_O_LEVEL $FORTIFY_SOURCE $CFLAGS" ;; | ||
21 | + yes,) CFLAGS="$CC_O_LEVEL $FORTIFY_SOURCE $CFLAGS" ;; | ||
22 | + ,yes) CFLAGS="-g $CFLAGS" ;; | ||
23 | esac | ||
24 | |||
25 | CC_CHECK_CFLAGS_APPEND([\ | ||