diff options
| author | Sam James <sam@gentoo.org> | 2023-10-04 13:08:15 +0100 |
|---|---|---|
| committer | Sam James <sam@gentoo.org> | 2023-10-04 13:09:55 +0100 |
| commit | 8a9088a028b5c95c944c75d55797852c4d92c722 (patch) | |
| tree | ce746f8d9e91a3c139ec17e959a8fbb511043e20 /dev-python/google-api-python-client/google-api-python-client-2.100.0.ebuild | |
| parent | 6276392ffe07fa5910ae1f2885435128fc988db3 (diff) | |
| download | gentoo-8a9088a028b5c95c944c75d55797852c4d92c722.tar.gz gentoo-8a9088a028b5c95c944c75d55797852c4d92c722.tar.bz2 gentoo-8a9088a028b5c95c944c75d55797852c4d92c722.zip | |
media-libs/libvpx: allow _FORTIFY_SOURCE
Upstream have been disabling this for years, since 2011(!), for a (IMO)
misguided attempt to preserve ABI which isn't really possible w/ glibc
and its use of symbol versioning anyway in a backwards direction.
Fedora have also been patching this out for a while: https://src.fedoraproject.org/rpms/libvpx/blob/rawhide/f/libvpx-1.7.0-leave-fortify-source-on.patch
This feels especially important given libvpx had an RCE vulnerability only
last week.
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-python/google-api-python-client/google-api-python-client-2.100.0.ebuild')
0 files changed, 0 insertions, 0 deletions