From a1a7f0324ea8a19d508b88a67d33331fa4d697bb Mon Sep 17 00:00:00 2001 From: Sam James Date: Thu, 13 Nov 2025 11:13:16 +0000 Subject: [PATCH] net-vpn/tor: don't force -fcf-protection=full The user may have conflicting *FLAGS. Also, we enable it by default in profiles in the toolchain already. I meant to do this when initially committing but forgot to go back and add it. Signed-off-by: Sam James --- net-vpn/tor/tor-0.4.8.20.ebuild | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net-vpn/tor/tor-0.4.8.20.ebuild b/net-vpn/tor/tor-0.4.8.20.ebuild index 507b262a47ff8..a88b21268baaf 100644 --- a/net-vpn/tor/tor-0.4.8.20.ebuild +++ b/net-vpn/tor/tor-0.4.8.20.ebuild @@ -119,6 +119,8 @@ src_configure() { export ac_cv_lib_cap_cap_init=$(usex caps) export tor_cv_PYTHON="${EPYTHON}" + # Already set by default in profiles for our toolchain + export tor_cv_cflags__fcf_protection_full=no local myeconfargs=( --localstatedir="${EPREFIX}/var"