diff options
| author | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2023-08-08 09:27:54 -0300 |
|---|---|---|
| committer | Andreas K. Hüttel <dilfridge@gentoo.org> | 2023-08-17 23:37:28 +0200 |
| commit | 6135d50e44233d8c89ca788f78c669941ad09fb9 (patch) | |
| tree | 951627d0cc6c44e683b0a9def1660aca6fd121ec /stdio-common/vfprintf-process-arg.c | |
| parent | 5ea70cc02626d9b85f1570153873d8648a47bf95 (diff) | |
| download | glibc-6135d50e44233d8c89ca788f78c669941ad09fb9.tar glibc-6135d50e44233d8c89ca788f78c669941ad09fb9.tar.gz glibc-6135d50e44233d8c89ca788f78c669941ad09fb9.tar.bz2 glibc-6135d50e44233d8c89ca788f78c669941ad09fb9.zip | |
x86_64: Fix build with --disable-multiarch (BZ 30721)
With multiarch disabled, the default memmove implementation provides
the fortify routines for memcpy, mempcpy, and memmove. However, it
does not provide the internal hidden definitions used when building
with fortify enabled. The memset has a similar issue.
Checked on x86_64-linux-gnu building with different options:
default and --disable-multi-arch plus default, --disable-default-pie,
--enable-fortify-source={2,3}, and --enable-fortify-source={2,3}
with --disable-default-pie.
Tested-by: Andreas K. Huettel <dilfridge@gentoo.org>
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
(cherry picked from commit 51cb52214fcd72849c640b12f5099ed3ac776181)
Diffstat (limited to 'stdio-common/vfprintf-process-arg.c')
0 files changed, 0 insertions, 0 deletions