diff options
| author | V3n3RiX <venerix@koprulu.sector> | 2023-03-17 06:26:48 +0000 |
|---|---|---|
| committer | V3n3RiX <venerix@koprulu.sector> | 2023-03-17 06:26:48 +0000 |
| commit | 2e0bf408961ec1023d3db1fc5d687c233661ac26 (patch) | |
| tree | 96c6e46af3c356d1fb470acdf72ada482bb293f8 /sys-libs/glibc/glibc-9999.ebuild | |
| parent | 48dbe17904ac8ee6f006488d8f21734b0d253db4 (diff) | |
gentoo auto-resync : 17:03:2023 - 06:26:48
Diffstat (limited to 'sys-libs/glibc/glibc-9999.ebuild')
| -rw-r--r-- | sys-libs/glibc/glibc-9999.ebuild | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/sys-libs/glibc/glibc-9999.ebuild b/sys-libs/glibc/glibc-9999.ebuild index df348d783cb1..f5ec71d81a7b 100644 --- a/sys-libs/glibc/glibc-9999.ebuild +++ b/sys-libs/glibc/glibc-9999.ebuild @@ -472,7 +472,18 @@ setup_flags() { filter-flags '-fsanitize=*' # See end of bug #830454; we handle this via USE=cet - filter-flags '-fcf-protection=' + filter-flags '-fcf-protection=*' + + # When bootstrapping, we may have a situation where + # CET-enabled gcc from seed is used to build CET-disabled + # glibc. As such, gcc implicitly enables CET if no + # -fcf-protection flag is passed. For a typical package it + # should not be a problem, but for glibc it matters as it is + # dealing with CET in ld.so. So if CET is supposed to be + # disabled for glibc, be explicit about it. + if (use amd64 || use x86) && ! use cet; then + append-flags '-fcf-protection=none' + fi } use_multiarch() { |