diff options
| author | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2024-09-10 09:22:17 -0300 |
|---|---|---|
| committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2024-10-01 08:44:40 -0300 |
| commit | 127cefd84dc551a43d0ac58b4619503d04869042 (patch) | |
| tree | cf6d1e255d280933a84dece69b4020843ce49f8d /wcsmbs | |
| parent | 9dfea3de7f690bff70e3c6eb346b9ad082bb2e35 (diff) | |
| download | glibc-127cefd84dc551a43d0ac58b4619503d04869042.zip glibc-127cefd84dc551a43d0ac58b4619503d04869042.tar.gz glibc-127cefd84dc551a43d0ac58b4619503d04869042.tar.bz2 | |
Do not use -Wp to disable fortify (BZ 31928)
The -Wp does not work properly if the compiler is configured to enable
fortify by default, since it bypasses the compiler driver (which defines
the fortify flags in this case).
This patch is similar to the one used on Ubuntu [1].
I checked with a build for x86_64-linux-gnu, i686-linux-gnu,
aarch64-linux-gnu, s390x-linux-gnu, and riscv64-linux-gnu with
gcc-13 that enables the fortify by default.
Co-authored-by: Matthias Klose <matthias.klose@canonical.com>
[1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/glibc/tree/debian/patches/ubuntu/fix-fortify-source.patch
Reviewed-by: DJ Delorie <dj@redhat.com>
Diffstat (limited to 'wcsmbs')
| -rw-r--r-- | wcsmbs/Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/wcsmbs/Makefile b/wcsmbs/Makefile index 63adf0e..37a44e6 100644 --- a/wcsmbs/Makefile +++ b/wcsmbs/Makefile @@ -264,7 +264,7 @@ CFLAGS-wcstod_l.c += $(strtox-CFLAGS) $(config-cflags-wno-ignored-attributes) CFLAGS-wcstold_l.c += $(strtox-CFLAGS) $(config-cflags-wno-ignored-attributes) CFLAGS-wcstof128_l.c += $(strtox-CFLAGS) CFLAGS-wcstof_l.c += $(strtox-CFLAGS) $(config-cflags-wno-ignored-attributes) -CPPFLAGS-tst-wchar-h.c += $(no-fortify-source),-D_FORTIFY_SOURCE=2 +CPPFLAGS-tst-wchar-h.c += $(no-fortify-source) -D_FORTIFY_SOURCE=2 CFLAGS-wcschr.c += $(config-cflags-wno-ignored-attributes) CFLAGS-wmemchr.c += $(config-cflags-wno-ignored-attributes) |